skills.rest
zillabunny
zillabunnyCOMMUNITY
Explore all skills by this author →
GitHub

fix-report

Review unreported sprint results and land validated fixes to main.

Updated Apr 2, 2026
Search Tags:#git#workflow#verification#report#sprint#landing
One-click install
npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill fix-report-zillabunny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix-report
Source: https://github.com/zillabunny/GoblinVolleyball-1.1/tree/main/.claude/skills/fix-report
Command: npx skills add https://github.com/zillabunny/GoblinVolleyball-1.1 --skill fix-report-zillabunny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review ALL unreported sprint results: walk through manual verifications, land fixes to main, close GitHub issues, update trackers, and clean up worktrees. Covers the current SPRINT_REPORT.md AND any landed-but-unclosed issues from previous sprints.

Core Features & Use Cases

  • Interactive, stepwise review of unfinalized sprints
  • Consolidated visibility across multiple sprints and issues
  • Safe landing workflow with explicit user prompts and STOP AND WAIT

Quick Start

Start the guided sprint-review flow by initiating the /fix-report command and following the prompts.

Frequently Asked Questions about fix-report

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review unreported sprint results and land validated fixes to main?▼

To review unreported sprint results and land validated fixes, use a guided sprint-review flow that walks through manual verifications, cherry-picks fixes to main, updates trackers, and closes GitHub issues with explicit user prompts.

What is the best way to consolidate multiple unfinalized sprints into a unified action plan?▼

Consolidating multiple unfinalized sprints requires a stepwise review process that gathers landed-but-unclosed issues from previous sprints, applies cherry-pick handling, and enforces a formal finalization gate to produce a unified, actionable plan.

How does the sprint finalization gate work when closing GitHub issues?▼

The sprint finalization gate works by enforcing explicit steps with STOP AND WAIT intervals between user prompts, ensuring fixes are fully validated and trackers are updated before GitHub issues are closed and worktrees are cleaned up.

Can I use a guided workflow to land cherry-picked fixes across previous sprints?▼

You can land cherry-picked fixes across previous sprints by initiating an interactive, stepwise review that identifies landed-but-unclosed issues, validates them, and safely lands them to main while updating all relevant trackers.

Why do I need STOP AND WAIT steps when landing fixes to main?▼

You need STOP AND WAIT steps when landing fixes to main to enforce safe landing guardrails, ensuring manual verifications are completed and validated before proceeding to close issues and clean up worktrees.

Does the sprint review process clean up worktrees after closing issues?▼

The sprint review process cleans up worktrees after closing GitHub issues, completing the finalization cycle by removing obsolete local branches once all fixes are landed and trackers are updated.

Related Skills

Explore More Software Engineering Skills→
lasswelltlasswellt
1

review

Automate sprint review and quality-gate checks with structured reports.

Community
Advanced
cowwoccowwoc
4

task-cleanup

Remove task branches and worktrees after merge to main.

Community
Intermediate
adamdriscolladamdriscoll

git-cherry-pick

Apply a specific Git commit from a source branch to a target branch.

Community
Intermediate
Knuckles-TeamKnuckles-Team
2

git-advanced

Automate Git history fixes using rebase, cherry-pick, and bisect workflows.

Official
Advanced