New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Piv Implement Issue

by coleam00 in coleam00/skills

Implement the fix for a GitHub issue from its RCA artifact (created by piv-investigate-issue) — drift-check the plan, branch, implement, add regression tests, and validate.

MITAuto-check passedTesting & QA

Install Piv Implement Issue

skills CLI
$ npx skills add coleam00/skills --skill piv-implement-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coleam00/skills piv-implement-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/piv-implement-issue .claude/skills/piv-implement-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
piv-implement-issue
GitHub stars
670
Token cost
~1.7k tokens
SKILL.md length
731 words
Files
1
Skills in repo
34
Repo updated
First seen
Licence
MIT

At a glance

Implement the fix for a GitHub issue from its RCA artifact (created by piv-investigate-issue) — drift-check the plan, branch, implement, add regression tests, and validate.

  • Works in 7 steps: Read and Understand RCA → Verify Current State — and check for drift → Implement the Fix → …
  • Testing & QA work in your project
  • SKILL.md covers Prerequisites, RCA Document to Reference, Implementation Instructions and Output Report, plus 1 more section
  • Calls gh and git

What it does

Piv Implement Issue is an agent skill from coleam00/skills. Implement the fix for a GitHub issue from its RCA artifact (created by piv-investigate-issue) — drift-check the plan, branch, implement, add regression tests, and validate. Use after the investigation artifact exists and you're ready to fix the issue.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA. It works with GitHub and Git. The repository describes itself as: The agent skills I actually use to build software with coding agents. The PIV loop, planning, worktrees, and the meta-skills for building your own AI Layer. The licence is MIT.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/piv-implement-issue”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(ruff:*), Bash(mypy:*), Bash(pytest:*), Bash(npm:*), Bash(bun:*)

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Read and Understand RCA
  2. Verify Current State — and check for drift
  3. Implement the Fix
  4. Add/Update Tests
  5. Run Validation
  6. Verify Fix
  7. Update Documentation

What it can do on your machine

Read from SKILL.md and the folder at commit 847be08. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(ruff:*)
    • Bash(mypy:*)
    • Bash(pytest:*)
    • Bash(npm:*)
    • Bash(bun:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Piv Implement Issue loads about 1.7k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 731 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coleam00/skills at commit 847be08, republished under its MIT licence (© coleam00). 731 words, ~1,685 tokens.

Download SKILL.mdSave it as .claude/skills/piv-implement-issue/SKILL.md (or your agent's skills folder).
name
piv-implement-issue
description
Implement the fix for a GitHub issue from its RCA artifact (created by piv-investigate-issue) — drift-check the plan, branch, implement, add regression tests, and validate. Use after the investigation artifact exists and you're ready to fix the issue.
allowed-tools
Read, Write, Edit, Bash(ruff:*), Bash(mypy:*), Bash(pytest:*), Bash(npm:*), Bash(bun:*)
argument-hint
github-issue-id

Implement Issue Fix: GitHub Issue #$ARGUMENTS

Prerequisites

This skill implements fixes for GitHub issues based on RCA documents:

  • Working in a local Git repository with GitHub origin
  • RCA document exists at docs/issues/issue-$ARGUMENTS.md
  • GitHub CLI installed and authenticated (optional, for status updates)

RCA Document to Reference

Read RCA: docs/issues/issue-$ARGUMENTS.md

Optional - View GitHub issue for context:

bash
gh issue view $ARGUMENTS

Implementation Instructions

1. Read and Understand RCA
  • Read the ENTIRE RCA document thoroughly
  • Review the GitHub issue details (issue #$ARGUMENTS)
  • Understand the root cause
  • Review the proposed fix strategy
  • Note all files to modify
  • Review testing requirements
2. Verify Current State — and check for drift

Before making changes:

  • Confirm the issue still exists.
  • Drift check: read each file the RCA names and compare against the RCA's "current code" snippets / line refs. If the code has changed materially since the RCA, stop — surface the drift and suggest re-running piv-investigate-issue for issue #$ARGUMENTS rather than implementing a stale plan.
  • Confirm the proposed fix still addresses the root cause — don't silently deviate.
2b. Get on the right branch
  • In a worktree? Use it (it was created for this work).
  • On the base branch, clean tree? Create a fix branch — git checkout -b fix/issue-$ARGUMENTS-<slug> (detect the base with git symbolic-ref refs/remotes/origin/HEAD; never hardcode main).
  • Already on a feature/fix branch? Use it (warn if its name doesn't reference #$ARGUMENTS).
  • Dirty tree on the base branch? Stop — ask the user to commit or stash first.
3. Implement the Fix

Following the "Proposed Fix" section of the RCA:

For each file to modify:

a. Read the existing file
  • Understand current implementation
  • Locate the specific code mentioned in RCA
b. Make the fix
  • Implement the change as described in RCA
  • Follow the fix strategy exactly
  • Maintain code style and conventions
  • Add comments if the fix is non-obvious
  • Update any related code affected by the fix
  • Ensure consistency across the codebase
  • Update imports if needed

Stay on plan: implement what the RCA specifies — don't refactor unrelated code or add unplanned "improvements." If you must deviate, note what changed and why, and surface it in the report (and the PR).

4. Add/Update Tests

Following the "Testing Requirements" from RCA:

Create test cases for:

  1. Verify the fix resolves the issue
  2. Test edge cases related to the bug
  3. Ensure no regression in related functionality
  4. Test any new code paths introduced

Test file location:

  • Follow project's test structure
  • Mirror the source file location
  • Use descriptive test names

Test implementation:

python
def test_issue_$ARGUMENTS_fix():
    """Test that issue #$ARGUMENTS is fixed."""
    # Arrange - set up the scenario that caused the bug
    # Act - execute the code that previously failed
    # Assert - verify it now works correctly
5. Run Validation

Execute validation commands from RCA:

bash
# Run linters
[from RCA validation commands]

# Run type checking
[from RCA validation commands]

# Run tests
[from RCA validation commands]

If validation fails:

  • Fix the issues
  • Re-run validation
  • Don't proceed until all pass
Show full SKILL.md (302 more words)Show less
6. Verify Fix

Manually verify:

  • Follow reproduction steps from RCA
  • Confirm issue no longer occurs
  • Test edge cases
  • Check for unintended side effects
7. Update Documentation

If needed:

  • Update code comments
  • Update API documentation
  • Update README if user-facing
  • Add notes about the fix

Output Report

Fix Implementation Summary

GitHub Issue #$ARGUMENTS: [Brief title]

Issue URL: [GitHub issue URL]

Root Cause (from RCA): [One-line summary of root cause]

Changes Made

Files Modified:

  1. [file-path]

    • Change: [What was changed]
    • Lines: [Line numbers]

  2. [file-path]

    • Change: [What was changed]
    • Lines: [Line numbers]
Tests Added

Test Files Created/Modified:

  1. [test-file-path]
    • Test cases: [List test functions added]

Test Coverage:

  • ✅ Fix verification test
  • ✅ Edge case tests
  • ✅ Regression prevention tests
Validation Results
bash
# Linter output
[Show lint results]

# Type check output
[Show type check results]

# Test output
[Show test results - all passing]
Verification

Manual Testing:

  • ✅ Followed reproduction steps - issue resolved
  • ✅ Tested edge cases - all pass
  • ✅ No new issues introduced
  • ✅ Original functionality preserved
Deviations from the RCA

[None — implemented as specified | List each deviation from the RCA + why]

Files Summary

Total Changes:

  • X files modified
  • Y files created (tests)
  • Z lines added
  • W lines removed
Ready for Commit

All changes complete and validated. Ready for the piv-commit skill.

Suggested commit message:

fix(scope): resolve GitHub issue #$ARGUMENTS - [brief description]

[Summary of what was fixed and how]

Fixes #$ARGUMENTS

Note: Using Fixes #$ARGUMENTS in the commit message will automatically close the GitHub issue when merged to the default branch.

Optional: Update GitHub Issue

Add implementation comment to issue:

bash
gh issue comment $ARGUMENTS --body "Fix implemented in commit [commit-hash]. Ready for review."

Update issue labels (if needed):

bash
gh issue edit $ARGUMENTS --add-label "fixed" --remove-label "bug"

Close the issue (if not using auto-close via commit message):

bash
gh issue close $ARGUMENTS --comment "Fixed and merged."

Notes

  • If the RCA document is missing or incomplete, request it be created first with the piv-investigate-issue skill for issue #$ARGUMENTS
  • If you discover the RCA analysis was incorrect, document findings and update the RCA
  • If additional issues are found during implementation, note them for separate GitHub issues and RCAs
  • Follow project coding standards exactly
  • Ensure all validation passes before declaring complete
  • The commit message Fixes #$ARGUMENTS will link the commit to the GitHub issue

© coleam00, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/piv-implement-issue of coleam00/skills.

Open the folder on GitHubat commit 847be08

Compare with similar skills

Piv Implement Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Piv Implement Issue compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Piv Implement Issue this skillcoleam00/skills670—~1.7kAutomated safety check: PassMIT
Nemoclaw Maintainer Fix E2E FailuresNVIDIA/NemoClaw23k—~2.6kAutomated safety check: PassApache-2.0
Reprovaadin/web-components582—~1.3kAutomated safety check: PassNone
Release Lambda LayerDataDog/datadog-lambda-js126—~1.8kAutomated safety check: PassApache-2.0
Reprovaadin/flow-components129—~1.3kAutomated safety check: PassNone
Close Flaky IssuesClickHouse/ClickHouse50k—~1.9kAutomated safety check: NotesApache-2.0

Similar skills

  • Nemoclaw Maintainer Fix E2E Failures

    NVIDIA/NemoClaw

    Official

    Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.

    23k GitHub stars~2.6k tokensUpdated today
    Testing & QAAuto-check passed

  • Repro

    vaadin/web-components

    Reproduce a Vaadin web component bug from a GitHub issue in vaadin/web-components.

    582 GitHub stars~1.3k tokensUpdated today
    Testing & QAAuto-check passed

  • Release Lambda Layer

    DataDog/datadog-lambda-js

    Official

    Walks through releasing a new datadog-lambda-js Lambda layer version — the automated Commercial release (version bump, tag, GitLab sign/publish jobs, npm publish, GitHub release) and the manual…

    126 GitHub stars~1.8k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Repro

    vaadin/flow-components

    Reproduce a Vaadin Flow component bug from a GitHub issue in vaadin/flow-components or a component-specific issue in vaadin/flow.

    129 GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Close Flaky Issues

    ClickHouse/ClickHouse

    Audit open "flaky test" GitHub issues and close those whose tests are no longer failing on master.

    50k GitHub stars~1.9k tokensUpdated today
    Testing & QAAuto-check: notes

  • MAUI UI Test Writer

    dotnet/maui

    Official

    Writes UI tests that reproduce a GitHub issue in .NET MAUI and keeps iterating until the tests actually fail, proving they catch the bug.

    23k GitHub stars~3k tokensUpdated today
    Testing & QAAuto-check passed

More from coleam00/skills

All 34 skills in this repo

  • Ablate AI Layer

    coleam00/skills

    Measure whether a repository's AI instructions still earn their place, by running the same real task many times with the layer intact and with it stripped, then grading every rule against what…

    670 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Build Dark Factory

    coleam00/skills

    Take a PRD and build a dark factory around it - a repository that takes work in as an issue and ships validated code out with nobody at the keyboard - one component at a time, into the user's actual…

    670 GitHub stars~12k tokensUpdated today
    Auto-check passed

  • Drive Screen

    coleam00/skills

    Take real control of the desktop - list and focus windows, type, paste, click, scroll, and screenshot - on Windows, macOS or Linux, and drive other coding-agent sessions running in terminals.

    670 GitHub stars~5.4k tokensUpdated today
    Auto-check passed

  • Second Brain Audit

    coleam00/skills

    Audit any second brain, notes folder, or agent memory for facts that have quietly stopped being true, then fix the worst one so it stops recurring.

    670 GitHub stars~4.6k tokensUpdated today
    Auto-check passed

  • Build Signal Engine

    coleam00/skills

    Build a personal signal engine from scratch - a system that reads every source someone cares about each day (changelogs and release notes, communities, feeds, videos, papers), makes a quick decision…

    670 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Worktree Create

    coleam00/skills

    Create one or more git worktrees for parallel development, each on its own branch with gitignored config copied in, dependencies installed, and a health check, by fanning out a setup subagent per…

    670 GitHub stars~958 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Piv Implement Issue

What does Piv Implement Issue do?

Implement the fix for a GitHub issue from its RCA artifact (created by piv-investigate-issue) — drift-check the plan, branch, implement, add regression tests, and validate. Piv Implement Issue is an agent skill from coleam00/skills. Implement the fix for a GitHub issue from its RCA artifact (created by piv-investigate-issue) — drift-check the plan, branch, implement, add regression tests, and validate.

When should I use Piv Implement Issue?

Piv Implement Issue fits situations like: testing & QA work in your project.

How do I install Piv Implement Issue in Claude Code?

Run `npx skills add coleam00/skills --skill piv-implement-issue -a claude-code`. Or copy the skill folder (.claude/skills/piv-implement-issue in coleam00/skills) into .claude/skills/piv-implement-issue in your project. Claude Code loads it when a task matches its description.

How do I install Piv Implement Issue in Codex?

Run `npx skills add coleam00/skills --skill piv-implement-issue -a codex`. Or copy the skill folder (.claude/skills/piv-implement-issue in coleam00/skills) into .agents/skills/piv-implement-issue in your project. Codex loads it when a task matches its description.

Can I use Piv Implement Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coleam00/skills --skill piv-implement-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/piv-implement-issue, .gemini/skills/piv-implement-issue, .github/skills/piv-implement-issue and .opencode/skills/piv-implement-issue in your project.

What does Piv Implement Issue need to run?

Going by SKILL.md and its folder, Piv Implement Issue needs the command-line tools its instructions call (gh and git). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(ruff:*), Bash(mypy:*), Bash(pytest:*), Bash(npm:*), Bash(bun:*).

Does Piv Implement Issue access the network?

SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Piv Implement Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Piv Implement Issue use?

Piv Implement Issue is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Piv Implement Issue use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Piv Implement Issue?

Skills that share tags, products or a category with Piv Implement Issue: Nemoclaw Maintainer Fix E2E Failures (NVIDIA/NemoClaw, 23k stars), Repro (vaadin/web-components, 582 stars), Release Lambda Layer (DataDog/datadog-lambda-js, 126 stars) and Repro (vaadin/flow-components, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Piv Implement Issue?

coleam00 (a GitHub user) maintains it in coleam00/skills, which has 670 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 7, 2026.

Source: coleam00/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.