Generate player-facing patch notes from git history, sprint data, and internal changelogs. Translates developer language into clear, engaging player communication.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
version: release version (e.g., 1.2.0). If missing, ask user.--style: brief (bullets), detailed (with context, default), full (+ developer commentary).Read: production/releases/[version]/changelog.md, docs/CHANGELOG.md entry, git log between tags (fallback), sprint retrospectives, balance change docs, QA bug fix records.
No data found → "Run /changelog [version] first." Verdict: BLOCKED.
Check for tone/voice guidance in: .claude/docs/technical-preferences.md, docs/PATCH-NOTES-STYLE.md, design/community/tone-guide.md. Default: player-friendly, non-technical, enthusiastic not hyperbolic, focus on player experience.
Use the project's own template at docs/patch-notes-template.md if it exists; otherwise .claude/docs/templates/release-notes.md (player-facing: headline, what's new, gameplay changes, fixes). Either one replaces the built-in styles.
Categories: New Content, Gameplay Changes, Quality of Life, Bug Fixes (by system), Performance, Known Issues.
Translation: dev language → player language ("Refactored damage pipeline" → "Improved hit detection accuracy"). Remove purely internal changes. Preserve specific numbers for balance changes (50→45).
No internal jargon, no ticket/sprint references, balance with before/after, bug fixes describe player experience, tone matches game voice.
Present notes + change count by category + excluded internal changes. "May I write to docs/patch-notes/[version].md?" Also archive to production/releases/[version]/patch-notes.md.
Verdict: COMPLETE. Run /release-checklist for other gates. Share draft with community-manager for tone review.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.
The English summary is being prepared. Showing the original description.
Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.
The English summary is being prepared. Showing the original description.
Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.
The English summary is being prepared. Showing the original description.
Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.
The English summary is being prepared. Showing the original description.
Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.
The English summary is being prepared. Showing the original description.
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.
The English summary is being prepared. Showing the original description.