mjmorales/auto-docs
skills/auto-docs/SKILL.md
Analyze scope and delegate to docs-writer and/or agentic-doc-writer. Triggers on "auto docs", "document everything", "generate docs".
$ install --global
skillsauthnpx skillsauth add mjmorales/claude-prove auto-docsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:59 AM18.8s1 file scanned
SKILL.md
- name:
- auto-docs
- description:
- Analyze scope and delegate to docs-writer and/or agentic-doc-writer. Triggers on "auto docs", "document everything", "generate docs".
Auto Docs
Orchestrate documentation generation by resolving scope, classifying subjects, and delegating to docs-writer and/or agentic-doc-writer. Follow references/interaction-patterns.md for all AskUserQuestion usage.
Workflow
- Resolve scope
- Classify subjects
- Confirm doc types, audience, output location with user
- Delegate to specialized skills
- Present results for approval
Step 1: Resolve Scope
| Input | Resolution | |-------|------------| | No argument | Session context: files read, written, edited, or discussed | | Topic name (e.g., "auth", "cafi") | Grep/Glob for matching files/packages/modules | | Directory path | All exported/public code in that directory | | File path(s) | Those specific files |
If ambiguous, AskUserQuestion header "Scope": "This session" / "Directory" / "Specific files".
Session Context Priority
- New files created this session
- Significantly modified files
- New agents/skills/commands
- Scripts
Skip: test files, lock files, build artifacts, self-documenting configs.
Step 2: Classify Subjects
| Subject Type | Indicators | Human Docs | Agent Docs |
|-------------|------------|------------|------------|
| Agent (agents/.md) | tools:/model: frontmatter | No | Yes |
| Skill (skills//SKILL.md) | name: frontmatter, workflow | Yes | Yes |
| Command (commands/.md) | description: frontmatter | Yes | No |
| Script (scripts/.sh) | Executable, CLI flags | Yes | Only if agents invoke it |
| Package/Module (src/, lib/) | Exports, public API | Yes | Yes |
| Config (.json, .yaml) | Schema, options | Yes | Only if agents read it |
Step 3: Confirm with User
AskUserQuestion header "Doc Types":
- "Both human & agent docs (Recommended)"
- "Human docs only"
- "Agent docs only"
- "Let me pick per subject"
If "Let me pick per subject": follow up with per-subject AskUserQuestion.
Audience (human docs): If not obvious, AskUserQuestion header "Audience": "Contributor" / "Consumer" / "Operator".
Output location: AskUserQuestion header "Output":
- "Alongside source (Recommended)"
- "Centralized docs/"
- "Let me specify"
Step 4: Delegate
Order: agent docs first (define contracts), then human docs (can reference contracts). Within each type, core modules before consumers.
docs-writer
Document [SUBJECT_TYPE]: [SUBJECT_NAME]
Audience: [AUDIENCE]
Source: [FILE_PATH]
Output: [OUTPUT_PATH]
Context:
[MINIMAL RELEVANT CODE/CONFIG]
agentic-doc-writer
Document [SUBJECT_TYPE]: [SUBJECT_NAME]
Source: [FILE_PATH]
Output: [OUTPUT_PATH]
Context:
[MINIMAL RELEVANT CODE/CONFIG]
Step 5: Review
Present summary table of generated docs (subject, human/agent, path, file count).
AskUserQuestion header "Review": "Approve all" / "Revise" / "Discard".
Committing
Delegate to commit skill. Example: docs(auto-docs): generate human and agent docs for cafi
Related Skills
mjmorales/janitor
tools
VerifiedTrustedCommunity
Clean and compact prove's durable memory layers — team Lore, the Codex (scrum decisions), annotations, and contributor artifacts — keeping the tribal knowledge that grows team accuracy and folding away the rot. Triggers on "janitor", "clean the lore", "compact the lore", "compact the codex", "memory cleanup", "clean up team memory", "prune stale decisions", "tidy tribal knowledge", "lore cleanup". You are the driver: the CLI emits inventories and executes writes; the `memory-janitor` agent judges each entry; a per-team batch gate approves; nothing is ever deleted — consolidation, promotion, and supersession only.
2SKILL.mdUpdated Jun 9, 2026
mjmorales/smart-compaction
testing
VerifiedTrustedCommunity
Anchor session context into prove primitives before compaction and rehydrate from them after. Built-in compaction summarizes by recency and drops the claude-prove state an agent needs to reorient; this skill externalizes volatile context into durable anchors (scrum tasks, decisions, run-state, a compact-anchors pointer file) pre-compact, then runs a deterministic reorientation sequence post-compact. Use before a manual /compact, when context is about to auto-compact, or immediately after a compaction. Triggers on "smart compact", "prepare for compaction", "anchor before compact", "context is getting long", "rehydrate", "reorient after compact".
2SKILL.mdUpdated Jun 5, 2026
mjmorales/run-migrate
tools
VerifiedTrustedCommunity
Apply model-driven CONTENT reshaping to stored run artifacts that sit behind the current schema, on explicit operator invocation only. Triggers on "migrate runs", "migrate run artifacts", "run content migration", "reshape run artifacts", "bring runs to current schema". You are the driver: the `run-state migrate-runs` CLI mechanically detects which artifacts are behind and emits a plan naming each one plus its migration-instruction file; you read the instructions and reshape the prose/findings, gated by the operator. The deterministic `schema migrate` handles structural column moves; this skill covers only the content reshaping beyond them. Never run as a background or resident loop — only when the operator asks.
2SKILL.mdUpdated Jun 5, 2026
mjmorales/reasoning-brief
tools
VerifiedTrustedCommunity
Synthesize the 7-section risk-forward Review Brief from a run's reasoning log. Triggers on "reasoning brief", "review brief", "synthesize the brief", "generate the brief", "brief the run", "brief for review", "story brief". You are the driver: the `acb brief` CLI renders a mechanical preservation-safe backbone and proves preservation; you synthesize the narrative prose (summary + changes), single-pass or multipass over episode chunks, then gate it through Stage-1 (mechanical, blocking) and Stage-2 (prose judge, advisory).
2SKILL.mdUpdated Jun 5, 2026