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
{{ message }}
This repository was archived by the owner on Oct 10, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: .context.md
+18-1Lines changed: 18 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -111,4 +111,21 @@ Each release goes through the following process:
111
111
5. Deployment to staging (documentation update)
112
112
6. Final approval and deployment to production (npm package release)
113
113
114
-
For more detailed information, please refer to the individual documents and subdirectories.
114
+
For more detailed information, please refer to the individual documents and subdirectories.
115
+
116
+
## Links for promotion / highlighting
117
+
118
+
The linter and the main README need to have good cross-linking. The NPM readme and the main readme are missing some things. There's been a new youtube video / press coverage of the idea. I want to give you those links and have you incorporate them in. Also the npm bullet at the top of the main readme isn't tracking the version number in npm properly.
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 Codebase Context Specification introduces a convention similar to `.env` and `.editorconfig` systems, but focused on documenting your code for both AI and humans. Just as `.env` files manage environment variables and `.editorconfig` ensures consistent coding styles, CCS files (`.context.md`, `.context.yaml`, `.context.json`) provide a standardized way to capture and communicate the context of your codebase.
@@ -35,11 +44,23 @@ The Codebase Context Specification is currently in a preview state. We're active
35
44
36
45
## Specification
37
46
38
-
For the full specification, please refer to [CODEBASE-CONTEXT.md](CODEBASE-CONTEXT.md).
47
+
For the full specification, please refer to [CODEBASE-CONTEXT.md](./CODEBASE-CONTEXT.md).
48
+
49
+
## Linter
50
+
51
+
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).
52
+
53
+
To install the linter:
54
+
55
+
```bash
56
+
npm install -g codebase-context-lint
57
+
```
58
+
59
+
For more information on using the linter, please refer to the [linter's README](./linters/typescript/README.md).
39
60
40
61
## Using with AI Assistants
41
62
42
-
The [CODING-ASSISTANT-PROMPT.md](CODING-ASSISTANT-PROMPT.md) file provides guidelines for AI assistants to understand and use the Codebase Context Specification. This allows for immediate adoption of the specification without requiring specific tooling integration.
63
+
The [CODING-ASSISTANT-PROMPT.md](./CODING-ASSISTANT-PROMPT.md) file provides guidelines for AI assistants to understand and use the Codebase Context Specification. This allows for immediate adoption of the specification without requiring specific tooling integration.
43
64
44
65
To use the Codebase Context Specification with an AI assistant:
45
66
@@ -54,12 +75,11 @@ Note that while this approach allows for immediate use of the specification, som
54
75
Developers are encouraged to create:
55
76
56
77
- Memory systems using git branches as storage
57
-
- Linters and validators for context files
58
78
- IDE plugins for context file creation and editing
59
79
- AI model integrations for parsing and utilizing context
60
80
- Tools for aggregating and presenting project-wide context
61
81
- Agents that can help create context in codebases that are blank
62
-
- Codebase summariziers, submodule summarizers
82
+
- Codebase summarizers, submodule summarizers
63
83
- Memory systems that take advantage of the context
64
84
- Continuous TODO monitors that can re-try implementations / solutions
65
85
@@ -77,16 +97,14 @@ We welcome contributions and feedback from the community to help shape the final
77
97
1.**Review the Specification**: Start by thoroughly reading the current specification in CODEBASE-CONTEXT.md.
78
98
2.**Open an Issue**: For suggestions, questions, or concerns, open an issue in this repository.
79
99
3.**Submit a Pull Request**: For proposed changes or additions, submit a pull request with a clear description of your modifications.
80
-
4.[**Join the Discussion**(https://github.com/Agentic-Insights/codebase-context-spec/discussions)]: Participate in open discussions and provide your insights on existing issues and pull requests.
100
+
4.[**Join the Discussion**](https://github.com/Agentic-Insights/codebase-context-spec/discussions): Participate in open discussions and provide your insights on existing issues and pull requests.
81
101
82
102
All contributions will be reviewed and discussed openly. Significant changes may go through an RFC (Request for Comments) process to ensure thorough consideration and community input.
83
103
84
104
## Version History
85
105
86
106
- 1.0-preview: Initial preview release of the Codebase Context Specification
For a deeper dive into the Codebase Context Specification, check out this [SubStack article by Vaskin](https://agenticinsights.substack.com/p/codebase-context-specification-rfc), the author of the specification.
Copy file name to clipboardExpand all lines: linters/typescript/README.md
+16-5Lines changed: 16 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,8 @@ This convention allows developers to:
33
33
34
34
By adopting this convention, teams can ensure that both human developers and AI assistants have access to crucial contextual information, leading to better code understanding, more accurate suggestions, and improved overall development efficiency.
35
35
36
+
For more detailed information about the Codebase Context Specification, please refer to the [main repository](https://github.com/Agentic-Insights/codebase-context-spec) and the [full specification](https://github.com/Agentic-Insights/codebase-context-spec/blob/main/CODEBASE-CONTEXT.md).
37
+
36
38
## 📦 Installation
37
39
38
40
You can install the linter globally using npm:
@@ -61,16 +63,14 @@ Replace `<directory_to_lint>` with the path to the directory containing your Cod
61
63
62
64
## 🤖 Using with AI Assistants
63
65
64
-
While this linter provides automated validation of CCS files, you can also use the Codebase Context Specification with AI assistants without any specific tooling. The [CODING-ASSISTANT-PROMPT.md](https://github.com/Agentic-Insights/codebase-context-spec/blob/main/CODING-ASSISTANT-PROMPT.md) file in the root directory provides guidelines for AI assistants to understand and use the Codebase Context Specification.
66
+
While this linter provides automated validation of CCS files, you can also use the Codebase Context Specification with AI assistants without any specific tooling. The [CODING-ASSISTANT-PROMPT.md](https://github.com/Agentic-Insights/codebase-context-spec/blob/main/CODING-ASSISTANT-PROMPT.md) file in the main repository provides guidelines for AI assistants to understand and use the Codebase Context Specification.
65
67
66
68
To use the Codebase Context Specification with an AI assistant:
67
69
68
70
1. Include the content of CODING-ASSISTANT-PROMPT.md in your prompt to the AI assistant.
69
71
2. Ask the AI to analyze your project's context files based on these guidelines.
70
72
3. The AI will be able to provide more accurate and context-aware responses by following the instructions in the prompt.
71
73
72
-
[A UI element graphic would be inserted here, demonstrating how the Codebase Context Specification could be integrated into development environments]
73
-
74
74
Note that while this approach allows for immediate use of the specification, some features like .contextignore should eventually be applied by tooling (such as this linter) for more robust implementation.
75
75
76
76
## 🛠️ Development
@@ -104,6 +104,17 @@ To contribute to this project:
104
104
7. Push to the branch (`git push origin feature/AmazingFeature`)
105
105
8. Open a Pull Request
106
106
107
-
## 📄 License
107
+
## � Learn More
108
+
109
+
For a deeper dive into the Codebase Context Specification, check out this [SubStack article by Vaskin](https://agenticinsights.substack.com/p/codebase-context-specification-rfc), the author of the specification.
0 commit comments