Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.
Quelldateien prüfen
Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
[Documentation] Use when you need to generate a detailed, AI-analyzed release document from git history over a time range or custom prompt.
triggers
["release doc","release document","release analysis","what changed in the last","changes in the last","generate release","release notes last","changes last 30 days","last N days"]
Quick Summary
Goal: Generate a detailed, AI-analyzed release document from git history — by time range (e.g., last 30 days) or custom comparison (e.g., v1.0.0..HEAD) or a user-described focus area.
Workflow:
Resolve Range — Determine the git range from user input
Dump Artifacts — Save log, file-status, and full diff to docs/release/ BEFORE analyzing
Categorize Changes — Group changed files by framework area (hooks, skills, agents, workflows, principles, config, docs)
Read Key Diffs — For each category, read the most significant changes via git show or git diff
Generate Doc — Write structured markdown release doc to docs/release/
Validate — Verify completeness and accuracy against the artifact files
Key Rules:
Dump first, read second — NEVER analyze a diff you haven't saved to a file first
Group by theme — Do not list commits chronologically; group by what area they impact
Cite evidence — Every section claim must reference a specific commit hash or file path
Custom focus honored — If user provides a focus prompt, weight that area more deeply
Draft status — All generated docs are Draft; add "Status: Draft" to the header
Release Doc Skill
Generate a detailed, narrative release document by analyzing git history over a time range or between two refs.
# Last 30 days
/release-doc --days 30
# Since a specific date
/release-doc --since 2026-03-15
# Between two tags or commits
/release-doc --range v1.0.0..HEAD
# With custom focus area
/release-doc --days 30 --focus "what changed in hooks and workflow enforcement"# Specify output file
/release-doc --days 30 --output docs/release/release-2026-Q1.md
For non-easy-claude projects, derive categories from the file path patterns actually present.
Step 4: Analyze Key Changes Per Category
For each category with significant changes (>5 files or >200 lines), read representative diffs:
# Most impactful commits (by files changed)
git log --since="$SINCE_DATE" --format="%H %s" --name-only | \
grep -A100 "^[a-f0-9]\{40\}" | head -200
# Show specific commit detail
git show {COMMIT_HASH} --stat --format="%s%n%b"# Diff for a specific file across the range
git diff ${OLDEST}^..HEAD -- .claude/hooks/init-prompt-gate.cjs
Analysis questions for each category:
Hooks: What new gates or enforcement were added? What context injection changed? What was the trigger behavior before vs after?
Skills: What new skills were created? What protocols were updated in existing skills? What was removed or merged?
Agents: What agent definitions changed? Did tool lists or dispatch rules change?
Workflows: What workflow steps were added/removed? Did sequence order change? Were any workflows merged or deleted?
Principles: What rules in CLAUDE.md changed? Were confidence thresholds tightened? New hard gates added?
Config: What new schema fields? What validation was added?
Scripts/Tooling: What new utilities? What improved or automated?
Evidence requirement: For every claim in the doc, record {commit_hash}:{file_path} as your source.
Step 5: Handle Custom Focus Prompt
If user provided --focus "...", apply additional depth to that area:
Grep all changed files matching the focus keywords
Read the full diff for matching files (not just stat)
Include a dedicated top-level section for the focus area in the output doc
Cross-reference related changes in other areas (e.g., a new skill + its hook + its workflow entry)
Step 6: Generate the Release Doc
Write to docs/release/release-notes-{PERIOD}.md (or --output path).
/release-notes — Use after /release-doc to generate a consumer-facing version (tag-to-tag, conventional commits)
/changelog — Use for individual feature changelog entries; /release-doc is for multi-week summaries
/graph-blast-radius — Run before release to assess impact of the most changed files
/docs-update — Update project reference docs after analyzing what changed
/commit — Commit the generated release doc
Troubleshooting
Diff too large for context
Solution: The skill requires artifact files be written first — never read the full diff into context. Use git show {hash} for individual commits and grep -l to narrow file scope.
Time range yields 0 commits
# Verify date format (ISO 8601)
git log --since="2026-03-15" --oneline | head -5
# If empty, check git's date interpretation:
git log --format="%ad" --date=short | head -5
Non-easy-claude project structure
The skill auto-derives categories from file paths. For repositories without .claude/, group by discovered source roots, tests, docs, scripts, and config paths instead.
Workflow Recommendation
MANDATORY IMPORTANT MUST ATTENTION — NO EXCEPTIONS: If you are NOT already in a workflow, use AskUserQuestion to ask the user:
Execute /release-doc directly (Recommended) — Standalone analysis and doc generation
Run /production-readiness-review + /quality-gate first — Pre-release quality gate, then release doc
Next Steps
MANDATORY IMPORTANT MUST ATTENTION — NO EXCEPTIONS after completing this skill, use AskUserQuestion to present:
"/release-notes (Recommended)" — Generate consumer-facing release notes from the same range
"/commit" — Commit the generated release doc to version control
"/docs-update" — Sync project reference docs with any changes discovered during analysis
"Skip, done" — User decides
[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting. This prevents context loss during large diff analysis. Always dump git artifacts to external files before reading.
External Memory: Write ALL intermediate findings and git artifacts to docs/release/ — this is MANDATORY. Large diffs will overflow context. Never try to hold a 30-day diff in memory.
Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).
AI Mistake Prevention — Failure modes to avoid on every task:
Re-read files after context changes. Context compaction, resume, or long-running work can make memory stale; verify current files before acting.
Verify generated content against source evidence. AI hallucinates APIs, names, claims, and document facts. Check the relevant source before documenting or referencing.
Check downstream references before deleting or renaming. Removing an artifact can stale docs, generated mirrors, configs, and callers; map references first.
Trace the full impact chain after edits. Changing a definition can miss derived outputs and consumers. Follow the affected chain before declaring done.
Verify ALL affected outputs, not just the first. One green check is not all green checks; validate every output surface the change can affect.
Assume existing values are intentional — ask WHY before changing. Before changing a constant, limit, flag, wording, or pattern, read nearby context and history.
Surface ambiguity before acting — don't pick silently. Multiple valid interpretations require an explicit question or stated assumption with risk.
Keep shared guidance role-relevant. Universal guidance must help every receiving skill or agent; code-specific obligations belong only in code-specific protocols.
Critical Thinking Mindset — Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence >80% to act.
Anti-hallucination: Never present guess as fact — cite sources for every claim, admit uncertainty freely, self-check output for errors, cross-reference independently, stay skeptical of own confidence — certainty without evidence root of all hallucination.
MUST ATTENTION apply critical + sequential thinking — every claim needs appropriate traced evidence (file:line for repo/code claims; source URL or artifact section for research, product, content, and docs claims); confidence >80% to act, <60% DO NOT recommend. Anti-hallucination: never present guess as fact, admit uncertainty freely, cross-reference independently, stay skeptical of own confidence.
MUST ATTENTION apply AI mistake prevention — verify generated content against evidence, trace downstream references before deleting or renaming, verify all affected outputs, re-read files after context loss, and surface ambiguity before acting.
Closing Reminders
Protocols in force (concise digest of the SYNC/shared blocks this skill carries):
AI Mistake Prevention: verify generated content against evidence, trace downstream references, verify all affected outputs, re-read after context loss, surface ambiguity.
Critical Thinking: traced file:line proof per claim, confidence >80% to act, never guess.
IMPORTANT MUST ATTENTION dump ALL git artifacts to docs/release/ BEFORE reading any diff content
IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting
IMPORTANT MUST ATTENTION cite commit hash + file path for every claim in the generated doc
IMPORTANT MUST ATTENTION add a final review task to validate completeness against artifact files
[TASK-PLANNING] Before acting, analyze task scope and systematically break it into small todo tasks and sub-tasks using TaskCreate.
