fix(core): correct commits path, fix typo, and remove stray code fence

## Why
`core/AGENTS.md` referenced a non-existent path (`~/.claude/core/commits.md`)
instead of the correct `~/.claude/core/instructions/commits.md`, and contained a
typo ("commiting" → "committing"). `core/instructions/commits.md` was wrapped in
an erroneous markdown code fence that caused agents reading the file to see it as
a raw text block rather than a live template with usable HTML comment sections.

## Impact
Agents following the content index in AGENTS.md will now resolve the correct path
for commit conventions. The commits template is now properly structured so its
comment-gated sections render as intended.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-06-27 14:02:31 +00:00
parent cd33ed9331
commit e09d1cd297
2 changed files with 17 additions and 18 deletions

View File

@@ -24,4 +24,4 @@ Read these files on demand:
- **Coding conventions** (`~/.claude/core/instructions/coding.md`) — when writing, editing, or reviewing code - **Coding conventions** (`~/.claude/core/instructions/coding.md`) — when writing, editing, or reviewing code
- **Git conventions** (`~/.claude/core/instructions/git.md`) — when doing git operations - **Git conventions** (`~/.claude/core/instructions/git.md`) — when doing git operations
- **Testing conventions** (`~/.claude/core/instructions/testing.md`) — when writing or running tests - **Testing conventions** (`~/.claude/core/instructions/testing.md`) — when writing or running tests
- **Git Commit conventions** (`~/.claude/core/commits.md`) — when commiting changes - **Git Commit conventions** (`~/.claude/core/instructions/commits.md`) — when committing changes

View File

@@ -1,16 +1,17 @@
```markdown <!--
# <type>(<scope>): <concise summary> <type>(<scope>): <concise summary>
# Required. Required.
#
# Purpose: Purpose:
# - Quickly communicates the intent when scanning `git log`. - Quickly communicates the intent when scanning `git log`.
# - Follow Conventional Commits for consistency and tooling. - Follow Conventional Commits for consistency and tooling.
# - Describe the intended outcome, not the implementation. - Describe the intended outcome, not the implementation.
#
# Examples: Examples:
# feat(auth): support OAuth device flow feat(auth): support OAuth device flow
# fix(cache): prevent stale session reuse fix(cache): prevent stale session reuse
# refactor(api): simplify request validation refactor(api): simplify request validation
-->
## Why ## Why
<!-- <!--
@@ -63,9 +64,8 @@ Omit if there are no noteworthy impacts.
--> -->
--- ---
# References (Git Trailers) # References
# Structured metadata for traceability and tooling. <!-- Git Trailers: Structured metadata for traceability and tooling. Use only the trailers that apply. -->
# Use only the trailers that apply.
Fixes: Fixes:
Refs: Refs:
@@ -76,4 +76,3 @@ Co-authored-by:
Reviewed-by: Reviewed-by:
Signed-off-by: Signed-off-by:
BREAKING CHANGE: BREAKING CHANGE:
```