revise-report-generation_skill

Overview

This skill generates structured revise reports for Epics by aggregating task comments, commit references, and screenshots into a single traceability and improvement document. It consolidates 'Revision Learning' comments across tasks, maps tasks to commits, and produces prioritized action items. Use it after an Epic is completed or substantially progressed to capture lessons learned and maintain traceability.

How this skill works

The skill queries the Epic’s child tasks and collects comments that start with Revision Learning:, Commit:, and Screenshots captured:. It extracts commit hashes, parses structured or freeform learnings into predefined categories (Documentation, Process, Rules & Standards, Tech Architecture), and groups screenshots by task. Finally, it builds a markdown revise report with an executive summary, traceability matrix, evidence section, categorized recommendations, and prioritized action items.

When to use it

• After an Epic is completed or substantially progressed to capture end-of-work learnings.
• When you need to consolidate Revision Learning comments from many tasks into one document.
• To produce a traceability report linking task IDs to commit hashes and subjects.
• Before retro or planning meetings to provide a concise improvement backlog.
• When verifying that PR review follow-up tasks are closed and lessons are finalized.

Best practices

• Ensure all follow-up PR review tasks are closed before running the report.
• Have authors add Revision Learning: and Commit: comments consistently on tasks.
• Prefer the structured Revision Learning format (Category, Priority, Issue, Recommendation) where possible.
• Keep screenshots in the declared screenshots directory and reference them in comments.
• Review the generated action items for clarity and assign owners and due dates immediately.

Example use cases

• Generate a post-delivery revise report for a feature Epic to capture technical debt and documentation gaps.
• Consolidate quality-gate failures and rework notes into process improvement recommendations.
• Create a traceability matrix for audit or compliance by mapping tasks to commit hashes.
• Produce a prioritized list of remediation tasks after a cross-team integration effort.
• Collect and link UI evidence (screenshots) to specific task learnings for design reviews.