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

refactor(bluecraft-agentic-docs): reorganize skill documentation and create linking patterns reference

Browse Source 
Restructure SKILL.md with clear triage workflow and reference selection guide.
Add dedicated linking-patterns.md reference with preferred patterns and anti-patterns.
Update root-agents-template.md and refactor-checklist.md to match new structure.
Expand agent interface description to include refactoring and cleanup scope.
This commit is contained in:
Ge Song
2026-04-20 13:09:12 +08:00
parent 4fa6e18940
commit 0987c0bf0e
5 changed files with 58 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
skills/bluecraft-agentic-docs/references/refactor-checklist.md
View File

@@ -5,11 +5,11 @@ Use this checklist after changing the root `AGENTS.md` or any file in `agent-doc
- Does each covered document own one clear topic?
- Does each filename clearly express the document's purpose?
- Does each opening explain purpose, trigger, and that the document must be followed in scope?
- Is the `AGENTS.md` at the root of the current Git working tree still the root entry document?
- Is the root `AGENTS.md` still the starting point for required `agent-docs`?
- Does every active `agent-docs/` file have an explicit path from the root?
- Does each child doc use the right shape for its job: rule doc versus inventory doc?
- Did you remove stale references, filenames, and replaced paths?
- Did you remove any orphan instruction docs created by the refactor?
- Did you delete or update any `agent-docs` file that is no longer referenced from the root `AGENTS.md`?
- Did you avoid duplicating the same rule across multiple active docs?
- Did you avoid mixing long entry inventories into rule docs when a separate inventory would be clearer?
- Is the default path basis still the root of the current Git working tree unless explicitly overridden?