메뉴
Merges ephemeral report and analysis artifacts into permanent documentation. Use when LLM-generated markdown files have accumulated and need consolidation.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/athola/claude-night-market --skill doc-consolidation명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Turn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.
Generates and self-executes a diff-derived test plan for a PR. Use when validating PR changes before merge. Do not use for code review; use sanctum:pr-review.
Curate the web-capture index. Use when the capture backlog grows, captures sit unprocessed at seedling/pending, or to surface stored research during work.
SKILL.md 표시 중
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 |
Extracts valuable knowledge from ephemeral LLM outputs and merges it into permanent documentation.
Use this skill when:
*_REPORT.md or *_ANALYSIS.md files from Claude sessionsDo NOT use when:
docs/, skills/)sanctum:doc-updates)scribe:slop-detector)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.
/consolidate-docs
Or invoke directly:
I have some report files that need consolidating into permanent docs.
Read-only analysis to generate a consolidation plan:
Checkpoint: User reviews and approves plan before execution.
After approval, performs the consolidation:
Load: @modules/candidate-detection.md
Identifies files using:
.md files)Load: @modules/content-analysis.md
For each candidate:
Load: @modules/destination-routing.md
For each valuable chunk:
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]
Load: @modules/merge-execution.md
After user approval:
Phase 1 tasks are delegated to haiku-class models for efficiency:
# plugins/sanctum/scripts/consolidation_planner.py handles:
- scan_for_candidates()
- extract_content_chunks()
- categorize_chunks()
- score_value()
- find_semantic_matches()
Phase 2 stays on the main model for careful merge execution.
| Category | Description | Default Destination |
|---|---|---|
| Actionable Items | Tasks, TODOs, next steps | docs/plans/YYYY-MM-DD-{topic}.md |
| Decisions Made | Architecture choices | docs/adr/NNNN-{date}-{topic}.md |
| Findings/Insights | Audit results, analysis | Best-match existing doc |
| Metrics/Baselines | Before/after comparisons | docs/benchmarks/ |
| Migration Guides | Step-by-step procedures | docs/migration-guide.md |
| API Changes | Breaking changes, deprecations | CHANGELOG or api docs |
Insert content into matching existing sections, preserving style.
Use when: Destination has relevant section, content is additive.
Replace existing section with more detailed new content.
Use when: New content 2x+ more detailed or has later date.
Add new section with date and source reference.
Use when: No matching section, content doesn't fit existing structure.
Generate complete new document.
Use when: No suitable destination exists, content warrants standalone doc.
Works with other sanctum skills:
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.
sanctum:doc-updates - General documentation updatessanctum:git-workspace-review - Pre-flight workspace analysissanctum:pr-prep - Pull request preparationimbue:catchup - Understanding recent changes*_REPORT.md, *_ANALYSIS.md, etc.)
are deleted after their content is successfully mergedgit status shows no untracked report-style markdown files
after consolidation completes