docs(extensions): clarify agent-context README and add config examples#3389
docs(extensions): clarify agent-context README and add config examples#3389yanukadeneth99 wants to merge 7 commits into
Conversation
Rewrite the agent-context extension README to read as plain prose instead of a bullet dump, and add the missing install/disable commands (specify extension add/disable/enable agent-context). Add inline example comments to agent-context-config.yml for context_file/context_files.
- Reformat comments to flow as single-line paragraphs instead of multi-line breaks - Add "WHAT" sections describing each configuration option's purpose - Add "REQUIREMENT" sections specifying if options are optional or required - Add explicit EXAMPLE sections for context_markers configuration - Improve clarity of context_file and context_files option descriptions
There was a problem hiding this comment.
Pull request overview
This PR updates the bundled agent-context extension documentation to better explain its opt-in behavior and configuration, and adds an explicit install command to the README.
Changes:
- Expanded
extensions/agent-context/README.mdwith installation/disabling instructions and clearer “opt-in” explanation. - Added more descriptive inline documentation and examples to
extensions/agent-context/agent-context-config.yml.
Show a summary per file
| File | Description |
|---|---|
| extensions/agent-context/README.md | Clarifies extension behavior and adds install/disable instructions; includes an Issues section link. |
| extensions/agent-context/agent-context-config.yml | Adds more explicit WHAT/REQUIREMENT/EXAMPLE guidance for config fields. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Low
- Fix "Github" -> "GitHub" casing in README issues link - Clarify agent-context-config.yml comments on context_file/context_files behavior and precedence
| All configuration flows through the extension's own config file at | ||
| `.specify/extensions/agent-context/agent-context-config.yml`: | ||
| [agent-context-config.yml](./agent-context-config.yml): | ||
|
|
||
| ```yaml | ||
| # Path to the coding agent context file managed by this extension |
There was a problem hiding this comment.
That section doesn't need to be explained because all information is there in the yml file itself. Removed the below yaml explanations but left in that line to mention the document path.
|
Please address Copilot feedback |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
- Clarify config file path reference (.specify/extensions path vs repo path) - Remove duplicated YAML example/field docs from README, point to config file directly - Minor spacing fix in agent-context-config.yml comment
|
Apologies for the delay! Should be all good now |
- Reference the installed .specify config path alongside the repo-relative link
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback
- README: clarify install command must be run from an initialized Spec Kit project root - config: correct context_markers requirement from REQUIRED to OPTIONAL
|
Done |
| # managed by this extension (e.g. CLAUDE.md, AGENTS.md, | ||
| # .github/copilot-instructions.md). Set automatically from the active | ||
| # integration and regenerated during `specify init` or integration switches. | ||
| # WHAT: Single project relative path to the main coding agent context file. |
|
|
||
| # Delimiters for the managed Spec Kit section. | ||
| # Edit these to use custom markers. | ||
| # WHAT: Markers (Delimiters) for the managed Spec Kit section. All information injected by this extension will only be done in between these markers. |
mnriem
left a comment
There was a problem hiding this comment.
Please address Copilot feedback
Description
Edited the
agent-contextREADME.mdandagent-context-config.ymlfor clarity. Added the missing install command.Testing
Ran the commands on a project to ensure it's correct. No other testing are required for this.
AI Disclosure
AI was used to check whether there were any active PRs/issues related to this, and then to create a suggested fix for the README. However, I only used that file as a reference and made the changes to the
README.mdmyself.Please do let me know if there are changes/suggestions to be done.