What problem does it solve? After fixing a bug, engineers often write vague or inconsistent resolution summaries that omit root causes, verification proof, or impact scope. This Skill enforces a rigorous report structure so reviewers and issue trackers get complete, technically sound documentation of what was fixed. ## Core Features & Use Cases - Evidence-first reporting: Requires capturing actual verification output (test results, build logs, before/after behavior) before drafting, with placeholder conventions for UI screenshots. - Standardized report skeleton: Generates a fixed structure covering PR link, root cause summary, per-file change entries (Bug/Purpose, Fix, Impact radius), and a verification block with real terminal output. - Strict writing rules: Bans self-reference, evolution language, and #123 shorthand, enforcing present-tense code-state descriptions and full GitHub URLs. - Use Case: After fixing a rendering bug on a branch, ask the agent to document the fix — it runs the verification command, diffs against the base branch, writes per-file change entries, and posts the report via gh pr edit or gh issue comment. ## Quick Start Ask the agent to write a resolution report for the fix on the current branch and post it as a comment on the GitHub issue.
