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

4
skills/agent-docs/references/repo-alignment-checklist.md
View File

@@ -4,9 +4,13 @@ Use this checklist when comparing AGENTS or `agent-docs` against repository fact
- Which exact doc claims depend on repository reality?
- Which repository files or commands provide the authoritative fact for each claim?
- For each item, did you record `doc claim`, `observed repo fact`, and `result` in that order?
- Do the rule docs expose enough authority or source-of-truth anchors that a maintainer can verify the claim without guessing?
- Which rules should have had an `Authority` section but do not?
- Do inventories that classify repository entities expose enough classification authority to verify their status or grouping decisions?
- Do scripts, ports, paths, or package names still match the docs?
- Do the documented verification commands still match actual script behavior?
- Do layering, contract-boundary, or runtime-topology claims still match code structure?
- Which mismatches are must-fix drift versus wording cleanup?
- Did every non-confirmed item include a severity level from the shared severity model?
- Are the conclusions grounded in current files and command output rather than memory?