You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+64-24Lines changed: 64 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,69 @@
8
8
9
9
Welcome to the [Codebase Context Specification (CCS)](./CODEBASE-CONTEXT.md) repository! This project establishes a standardized method for embedding rich contextual information within codebases to enhance understanding for both AI and human developers. By providing a clear and consistent way to communicate project structure, conventions, and key concepts, we significantly improve code comprehension and facilitate more effective collaboration between humans and AI in software development.
The linter will validate your .context.md, .context.yaml, .context.json, .contextdocs.md, and .contextignore files according to the Codebase Context Specification.
58
+
59
+
## Library Usage
60
+
61
+
You can also use the Codebase Context Linter as a library in your TypeScript or JavaScript projects:
Note: The linter will automatically create any necessary directories when writing files.
73
+
11
74
## Codebase Context Editor
12
75
13
76
To help you get started with creating context files for your project, we've developed the Codebase Context Editor. This tool simplifies the process of generating .context.md, .contextdocs.md, and .contextignore files that adhere to the Codebase Context Specification.
@@ -21,15 +84,6 @@ The Codebase Context Editor provides an intuitive interface for:
21
84
22
85
Whether you're new to the Codebase Context Specification or an experienced user, the editor can significantly streamline your workflow.
This project supports the following Node.js versions:
@@ -59,20 +113,6 @@ By adopting this convention, teams can ensure that both human developers and AI
59
113
-**Standardized Context Files**: Consistent use of `.context.md`, `.context.yaml`, and `.context.json` files for conveying codebase context at various levels (project-wide, directory-specific, etc.).
60
114
-**Context-Aware Development**: Encouraging a development approach that considers and documents the broader context of code, not just its immediate functionality.
61
115
62
-
## Linter
63
-
64
-
We provide a linter to help validate your context files according to the specification. You can find the NPM package here: [codebase-context-lint](https://www.npmjs.com/package/codebase-context-lint).
65
-
66
-
To install the linter:
67
-
68
-
```bash
69
-
npm install -g codebase-context-lint
70
-
```
71
-
72
-
Note: Make sure you're using a supported Node.js version (18.x, 20.x, or 22.x) when installing and running the linter.
73
-
74
-
For more information on using the linter, please refer to the [linter's README](./linters/typescript/README.md).
75
-
76
116
## Recent Updates
77
117
78
118
We've recently updated our dependencies to address security vulnerabilities and improve compatibility with different Node.js versions. If you encounter any issues after updating, please report them in our GitHub issues.
@@ -122,7 +162,7 @@ All contributions will be reviewed and discussed openly. Significant changes may
122
162
123
163
## Version History
124
164
125
-
- 1.0-preview: Initial preview release of the Codebase Context Specification
165
+
- 1.0.0-RFC: Initial RFC release of the Codebase Context Specification
0 commit comments