Nm Sanctum Doc Consolidation
by @athola
Merge report and analysis artifacts into permanent docs, then delete source files
β‘ When to Use
| Trigger | Action |
|---|
| - You have untracked `*_REPORT.md` or `*_ANALYSIS.md` files from Claude sessions |
| - Git status shows markdown files that shouldn't be committed but contain useful content |
| - You want to preserve insights from code reviews, refactoring reports, or API audits |
| - Preparing a PR and need to clean up working artifacts |
| Do NOT use when: |
| - Files are already in proper documentation locations |
| (`docs/`, `skills/`) |
| - Files are intentionally temporary scratch notes |
| - User explicitly wants to preserve the original report format |
| - Source files have no extractable value (pure log output) |
π‘ Examples
/consolidate-docs
Or invoke directly:
I have some report files that need consolidating into permanent docs.
π Tips & Best Practices
No candidates found
Check git status for untracked files
Files may already be in standard locations
Try explicit file path: "Consolidate API_REVIEW_REPORT.md"Low-quality extractions
Source file may lack structured sections
Content may be too generic to categorize
Try manual extraction for unstructured reportsMerge conflicts
Destination file structure changed
Try APPEND strategy instead of WEAVE
Manual intervention may be neededclawhub install nm-sanctum-doc-consolidation
π§ͺ Use this skill with your agent
Most visitors already have an agent. Pick your environment, install or copy the workflow, then run the smoke-test prompt above.
π Can't find the right skill?
Search 60,000+ AI agent skills β free, no login needed.
