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

split agent-docs skills

Browse Source
This commit is contained in:
Ge Song
2026-04-23 01:29:16 +08:00
parent 0987c0bf0e
commit 2c22fcc4c3
23 changed files with 679 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
skills/agent-docs/references/audit-checklist.md Normal file
View File

@@ -0,0 +1,14 @@
# Audit Checklist
Use this checklist for read-only audits of `AGENTS.md` and `agent-docs/`.
- Is the root `AGENTS.md` still the clear entrypoint?
- Can a maintainer tell which document to read first for each common task?
- Does any document act like a secondary router without enough reason?
- Does each rule appear to have one authoritative home?
- Does any inventory document contain policy language that should live in a rule doc?
- Does any general-purpose agent-doc mix in project-specific business rules, product instructions, or end-user documentation?
- Do key workflow docs state their edge cases and failure modes clearly enough that an agent would not have to infer them?
- Are there residual cycles or cross-links that materially increase adherence cost?
- Which findings are observed facts, and which are inferences about adherence risk?
- If there are no concrete findings, what residual risks remain?