Revise Report Generation
Generates structured revise reports for Epics by aggregating task comments and learnings. Use when: (1) An Epic is completed or substantially progressed, (2) You want to consolidate "Revision Learning" comments from multiple tasks, (3) You need a traceability report linking tasks to commits.
npx skills add majiayu000/claude-skill-registry --skill revise-report-generation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Revise Report Generation Generates structured revise reports to capture insights, learnings, and traceability from Beads Epics. ## Prerequisites - Beads Epic ID (e.g., `bd-1234`) - Beads CLI (`bd`) installed and configured - Tasks within the Epic populated with comments (specifically "Revision Learning" and "Commit") - Confirm there are no open follow-up tasks created from PR review comments (final review should create these first, and revise report runs only after they are closed) ## Report Structure ### Epic Revise Report **1. Epic Summary** - Status of the Epic and child tasks. - Overall completion rate. **2. Traceability Matrix** - Table mapping Task ID -> Title -> Status -> Commit Hash. **3. Evidence & Screenshots** - Screenshot directory location and count. - Key screenshots with descriptions and links. - Evidence organization by task. **4. Improvement Recommendations** - **Documentation:** Missing docs, outdated content, gaps in onboarding. - **Process:** Workflow friction, automation opportunities, quality gate improvements. - **Rules & Standards:** Cursor rules updates, coding standards violations, pattern inconsistencies. - **Tech Architecture:** Code structure issues,
- Prerequisites
- Report Structure
- Epic Revise Report
- Report Generation Process
- Step 1: Data Gathering
- Step 2: Analysis & Categorization
- Step 3: Report Construction
- Validation
What does the Revise Report Generation skill do?
Generates structured revise reports for Epics by aggregating task comments and learnings. Use when: (1) An Epic is completed or substantially progressed, (2) You want to consolidate "Revision Learning" comments from multiple tasks, (3) You need a traceability report linking tasks to commits.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill revise-report-generation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.