- [When to Use](#when-to-use)
/plugin marketplace add athola/claude-night-market/plugin install pensive@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/candidate-detection.mdmodules/content-analysis.mdmodules/destination-routing.mdmodules/merge-execution.mdscripts/consolidation_planner.pyExtracts 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/)/consolidate-docs
Verification: Run the command with --help flag to verify availability.
Or invoke directly:
**Verification:** Run the command with `--help` flag to verify availability.
I have some report files that need consolidating into permanent docs.
Verification: Run the command with --help flag to verify availability.
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]
Verification: Run the command with --help flag to verify availability.
Load: @modules/merge-execution.md
After user approval:
Phase 1 tasks are delegated to haiku-class models for efficiency:
# scripts/consolidation_planner.py handles:
- scan_for_candidates()
- extract_content_chunks()
- categorize_chunks()
- score_value()
- find_semantic_matches()
Verification: Run the command with --help flag to verify availability.
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:
**Verification:** Run the command with `--help` flag to verify availability.
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.
Verification: Run the command with --help flag to verify availability.
sanctum:doc-updates - General documentation updatessanctum:git-workspace-review - Pre-flight workspace analysissanctum:pr-prep - Pull request preparationimbue:catchup - Understanding recent changesThis skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.