piv-implement-issue

Implement GitHub issue fixes from RCA documents with drift checks, regression tests, and validation.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-implement-issue-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: piv-implement-issue
Source: https://github.com/az9713/claude-code-hooks-tutorial/tree/main/skills/.claude/skills/piv-implement-issue
Command: npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-implement-issue-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Implementing a bug fix from a prior investigation often goes wrong when the code has drifted since the analysis, the fix happens on the wrong branch, or validation is skipped. This Skill turns a root-cause analysis document into a disciplined implementation workflow so the fix matches the plan and is fully tested. ## Core Features & Use Cases - Drift Detection: Compares the current code against the RCA's referenced snippets and stops if the plan is stale, suggesting a re-investigation instead of implementing an outdated fix. - Branch Management: Detects worktrees, creates a fix branch from the detected base branch, and refuses to proceed on a dirty base branch. - Regression Testing and Validation: Adds tests that verify the fix, cover edge cases, and run the RCA's lint, type-check, and test commands before declaring completion. - Use Case: After running an investigation that produced docs/issues/issue-42.md, invoke this Skill with the issue number to implement the planned fix, add regression tests, and produce a commit-ready summary with a Fixes #42 message. ## Quick Start Ask the agent to implement the fix for GitHub issue 42 using the RCA document at docs/issues/issue-42.md.

Frequently Asked Questions about piv-implement-issue

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

FAQPage Schema
How do I implement a fix for a GitHub issue from an RCA document?▼

Invoke the Skill with the issue number after the RCA exists at docs/issues/issue-<id>.md. It reads the RCA, verifies the code has not drifted, creates or reuses a fix branch, implements the planned changes, adds regression tests, and runs the validation commands.

What happens if the code changed since the root cause analysis was written?▼

The Skill performs a drift check by comparing current files against the RCA's code snippets and line references. If the code changed materially, it stops and recommends re-running the piv-investigate-issue Skill instead of implementing a stale plan.

Does this Skill require the GitHub CLI to work?▼

No, the GitHub CLI is optional. It is only used to view issue details and post status comments or label updates. The core implementation workflow relies on the local RCA document and Git.

Which branch does the fix get implemented on?▼

It uses an existing worktree or feature branch if present, otherwise it creates fix/issue-<id>-<slug> from the detected base branch via git symbolic-ref. It stops and asks you to commit or stash if the base branch has uncommitted changes.

What should I do if the RCA document is missing?▼

The Skill requires the RCA at docs/issues/issue-<id>.md before starting. If it is missing or incomplete, run the piv-investigate-issue Skill first to produce the root cause analysis, then return to implementation.