public/bluecraft
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

optimize agent-docs

Browse Source
This commit is contained in:
Ge Song
2026-04-23 02:16:39 +08:00
parent 2c22fcc4c3
commit c14adfc633
31 changed files with 734 additions and 377 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
skills/agent-docs-consistency/SKILL.md
View File

@@ -14,6 +14,7 @@ Use this skill for structural consistency checks across AGENTS and `agent-docs`.
- The user asks whether there are cycles
- The user asks for document depth or routing structure
- The user asks whether two docs both own the same rule
- The user asks whether two sibling docs both apply to the same task
- The user asks whether a doc has become a secondary router or mixed-shape document
## Workflow
@@ -21,21 +22,31 @@ Use this skill for structural consistency checks across AGENTS and `agent-docs`.
1. Read the root `AGENTS.md`.
2. Read the active child docs in scope.
3. Read `../agent-docs/references/consistency-checklist.md`.
4. Inspect:
4. Read `../agent-docs/references/severity-model.md`.
5. Read `../agent-docs/references/report-format.md`.
6. Inspect:
- root reachability
- shortest routing depth
- direct cycles and high-noise cross-links
- duplicate authority candidates
- equally specific overlapping docs
- out-degree hotspots
- rule-doc vs inventory-doc shape mismatches
5. Distinguish:
- blocking or high-noise structural problems
7. Apply the default structure budget unless a narrower doc explicitly justifies an exception:
- recommended shortest root-to-leaf routing depth: `<= 3`
- recommended active downstream references from one doc: `<= 7`
- treat budget overruns as structural warnings, then decide whether they remain acceptable or now require refactor
8. Distinguish:
- blocking structural ambiguity such as duplicate authority or equally specific overlapping docs
- other high-noise structural problems
- acceptable cross-references
6. Report the structural findings without drifting into repository implementation review. Use `agent-docs-repo-alignment` for repo-fact comparison.
9. Report the structural findings without drifting into repository implementation review. Use the consistency shape from `report-format.md`. Use `agent-docs-repo-alignment` for repo-fact comparison.
## Output
- Reachability summary
- Cycle summary
- Duplicate-authority or shape findings
- Blocking structural ambiguity findings
- Structural warnings such as depth or out-degree overruns
- Other duplicate-authority or shape findings
- Residual risk assessment