Skip to main content
doc-consolidation Merges ephemeral report and analysis artifacts into permanent documentation. Use when LLM-generated markdown files have accumulated and need consolidation.
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/athola/claude-night-market --skill doc-consolidationEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Explorador de archivos
5 archivos Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
name doc-consolidation description Merges ephemeral report and analysis artifacts into permanent documentation. Use when LLM-generated markdown files have accumulated and need consolidation. globs **/*.md alwaysApply false category documentation tags ["docs","consolidation","cleanup","git-hygiene","knowledge-management"] status stable created "2025-12-06T00:00:00.000Z" updated "2025-12-06T00:00:00.000Z" modules ["modules/candidate-detection.md","modules/content-analysis.md","modules/destination-routing.md","modules/merge-execution.md"] model_hint standard
Table of Contents
Doc Consolidation
Extracts valuable knowledge from ephemeral LLM outputs and merges it into permanent documentation.
When To Use
Use this skill when:
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)
When NOT To Use
Updating docs to match a code change (use sanctum:doc-updates)
Detecting AI patterns in prose (use scribe:slop-detector)
Formatting When merging content into permanent documentation, follow
Skill(leyline:markdown-formatting) conventions: wrap prose
at 80 chars (prefer sentence/clause boundaries), blank lines
around headings, ATX headings only, blank line before lists,
and reference-style links for long URLs.
Quick Start I have some report files that need consolidating into permanent docs.
Two-Phase Workflow
Phase 1: Triage (Fast Model) Read-only analysis to generate a consolidation plan:
Detect candidates - Find untracked markdown files with LLM output markersAnalyze content - Extract and categorize valuable sectionsRoute destinations - Match content to existing docs or propose new filesPresent plan - Show user what will be consolidated and where Checkpoint : User reviews and approves plan before execution.
Phase 2: Execute (Main Model) After approval, performs the consolidation:
Merge content - Weave into existing docs or create new filesDelete sources - Remove ephemeral files after successful mergeGenerate summary - Report what was created/updated/deleted
Workflow Details
Step 1: Candidate Detection Load: @modules/candidate-detection.md
Git status (untracked .md files)
Location (not in standard doc directories)
Naming (ALL_CAPS non-standard names)
Content markers (Executive Summary, Findings, Action Items)
Step 2: Content Analysis Load: @modules/content-analysis.md
Extract sections as content chunks
Categorize: Actionable Items, Decisions, Findings, Metrics, Migration Guides, API Changes
Score value: high/medium/low
Step 3: Destination Routing Load: @modules/destination-routing.md
Semantic match against existing documentation
Apply default mappings if no good match
Determine merge strategy (weave, replace, append, create)
Step 4: Generate Plan Present consolidation plan to user:
# Consolidation Plan
## Source: API_REVIEW_ REPORT.md
| Content | Category | Value | Destination | Action |
|---------|----------|-------|-------------|--------|
| API inventory | Findings | High | docs/api-overview.md | Create |
| Action items | Actionable | High | docs/plans/2025-12-06-api.md | Create |
### Post-Consolidation
- Delete: API_REVIEW_ REPORT.md
Proceed with consolidation? [Y/n]
Step 5: Execute Merges Load: @modules/merge-execution.md
Group operations by destination file
Apply merge strategies
Validate results (frontmatter intact, structure preserved)
Delete source files
Generate execution summary
Fast Model Delegation Phase 1 tasks are delegated to haiku-class models for efficiency:
- scan_for_candidates()
- extract_content_chunks()
- categorize_chunks()
- score_value()
- find_semantic_matches()
Phase 2 stays on the main model for careful merge execution.
Content Categories Category Description Default Destination Actionable Items Tasks, TODOs, next steps docs/plans/YYYY-MM-DD-{topic}.mdDecisions Made Architecture choices docs/adr/NNNN-{date}-{topic}.mdFindings/Insights Audit results, analysis Best-match existing doc Metrics/Baselines Before/after comparisons docs/benchmarks/Migration Guides Step-by-step procedures docs/migration-guide.mdAPI Changes Breaking changes, deprecations CHANGELOG or api docs
Merge Strategies
Intelligent Weave Insert content into matching existing sections, preserving style.
Use when: Destination has relevant section, content is additive.
Replace Section Replace existing section with more detailed new content.
Use when: New content 2x+ more detailed or has later date.
Append with Context Add new section with date and source reference.
Use when: No matching section, content doesn't fit existing structure.
Create New File Generate complete new document.
Use when: No suitable destination exists, content warrants standalone doc.
Integration Works with other sanctum skills:
git-workspace-review : May suggest consolidation when untracked reports detectedpr-prep : Warns about untracked analysis files before PR creationdoc-updates : Can invoke for final polish after consolidation
Example Session User: I have API_REVIEW_REPORT.md from our review session. Can you consolidate it?
Claude: I'll consolidate the report into permanent documentation.
**Phase 1: Triage**
Scanning for candidates...
- Found: API_REVIEW_REPORT.md (untracked, LLM markers detected)
Analyzing content...
- Extracted 6 content chunks
- High value: API inventory, action items, CLI recommendation
- Medium value: security assessment
- Low value: executive summary (generic)
Routing destinations...
- API inventory → docs/api-overview.md (CREATE)
- Action items → docs/plans/2025-12-06-api-consistency.md (CREATE)
- CLI naming → docs/adr/0002-cli-naming.md (CREATE ADR)
- Security → Already covered in docs/security.md (SKIP)
**Consolidation Plan**
[table shown]
Proceed? [Y/n]
User: Y
Claude: **Phase 2: Executing**
Created: docs/api-overview.md (1,247 bytes)
Created: docs/plans/2025-12-06-api-consistency.md (892 bytes)
Created: docs/adr/0002-2025-12-06-cli-naming.md (634 bytes)
Deleted: API_REVIEW_REPORT.md
Consolidation complete. Review the created files and commit when ready.
Troubleshooting
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 reports
Merge conflicts
Destination file structure changed
Try APPEND strategy instead of WEAVE
Manual intervention may be needed
Related Skills
sanctum:doc-updates - General documentation updatessanctum:git-workspace-review - Pre-flight workspace analysissanctum:pr-prep - Pull request preparationimbue:catchup - Understanding recent changes
Exit Criteria 