add support for CCS 1.0.0-RFC to boost context throughout the codebase

[killerapp]

Issue

Please add support for the Codebase Context Specification (CCS) in Aider. CCS allows developers to embed rich contextual information within codebases using standardized .context.md, .context.yaml, and .context.json files. This enhancement will improve Aider's ability to understand project structure, architecture, and conventions, leading to more accurate code suggestions and better AI-assisted development workflows.

Details:

• Implement parsing and interpretation of CCS files.
• Provide integration options to enable or disable CCS usage.
• Ensure backward compatibility with existing workflows.

References:

CCS GitHub Repository CCS Linter on npm Thank you!

Version and model info

No response

[andrewsgeller]

Doesn’t aider already use something similar with tree-sitter? What are the major differences? This sounds like a dream come true for us who have less coding experience and less expertise in explaining things in proper syntax to the LLM when requesting error fixes and code enhancements.

Sent from my iPhone

---

From: Vaskin Kissoyan @.> Sent: Sunday, September 1, 2024 9:43 AM To: paul-gauthier/aider @.> Cc: Subscribed @.***> Subject: [paul-gauthier/aider] add support for CCS 1.0.0-RFC to boost context throughout the codebase (Issue #1284)

Issue

Please add support for the Codebase Context Specification (CCS) in Aider. CCS allows developers to embed rich contextual information within codebases using standardized .context.md, .context.yaml, and .context.json files. This enhancement will improve Aider's ability to understand project structure, architecture, and conventions, leading to more accurate code suggestions and better AI-assisted development workflows.

Details:

• Implement parsing and interpretation of CCS files.
• Provide integration options to enable or disable CCS usage.
• Ensure backward compatibility with existing workflows.

References:

CCS GitHub Repositoryhttps://example.com/ CCS Linter on npmhttps://npmjs.com/package/codebase-context-lint Thank you!

Version and model info

No response

— Reply to this email directly, view it on GitHubhttps://github.com/paul-gauthier/aider/issues/1284, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJ65MRSSUI53VLNRI52QOADZUMKZHAVCNFSM6AAAAABNO3MQC2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQ4TSNBXG44TOOA. You are receiving this because you are subscribed to this thread.Message ID: @.***>

[ozapinq]

The first link leads to example.com

[killerapp]

The first link leads to example.com Fixed

https://github.com/Agentic-Insights/codebase-context-spec

[killerapp]

Doesn’t aider already use something similar with tree-sitter? What are the major differences? This sounds like a dream come true for us who have less coding experience and less expertise in explaining things in proper syntax to the LLM when requesting error fixes and code enhancements.

I am just now looking at https://tree-sitter.github.io/tree-sitter/

Yes, this would work WITH and enable tools like that to pull out MORE context directly in the tree from these files (structured and unstructured).

It gives the power of context enriching directly to the architect / codebase team.

Also, to better answer your question, this is just a spec, there is no tooling other than the linter for some of the structured stuff I'll be putting in like cross-codebase references.