OpenROAD Bug Fixer
The-OpenROAD-Project/OpenROAD
Fixes an OpenROAD bug from a GitHub issue or error code: finds the root cause, implements the fix, adds a regression test and prepares a signed-off commit.
Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue).
Install Piv Investigate Issue
$ npx skills add coleam00/skills --skill piv-investigate-issue -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install coleam00/skills piv-investigate-issue --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/piv-investigate-issue .claude/skills/piv-investigate-issue && rm -rf skills-srcUse ~/.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/
Install the "piv-investigate-issue" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-investigate-issue into .claude/skills/piv-investigate-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-investigate-issue", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/coleam00/skills/tree/main/.claude/skills/piv-investigate-issueType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add coleam00/skills --skill piv-investigate-issue -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install coleam00/skills piv-investigate-issue --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/piv-investigate-issue .agents/skills/piv-investigate-issue && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "piv-investigate-issue" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-investigate-issue into .agents/skills/piv-investigate-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-investigate-issue", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add coleam00/skills --skill piv-investigate-issue -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install coleam00/skills piv-investigate-issue --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/piv-investigate-issue .cursor/skills/piv-investigate-issue && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "piv-investigate-issue" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-investigate-issue into .cursor/skills/piv-investigate-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-investigate-issue", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/coleam00/skills.git --path .claude/skills/piv-investigate-issue--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add coleam00/skills --skill piv-investigate-issue -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install coleam00/skills piv-investigate-issue --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/piv-investigate-issue .gemini/skills/piv-investigate-issue && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "piv-investigate-issue" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-investigate-issue into .gemini/skills/piv-investigate-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-investigate-issue", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install coleam00/skills piv-investigate-issueInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add coleam00/skills --skill piv-investigate-issue -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/piv-investigate-issue .github/skills/piv-investigate-issue && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "piv-investigate-issue" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-investigate-issue into .github/skills/piv-investigate-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-investigate-issue", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add coleam00/skills --skill piv-investigate-issue -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install coleam00/skills piv-investigate-issue --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/coleam00/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/piv-investigate-issue .opencode/skills/piv-investigate-issue && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "piv-investigate-issue" agent skill from https://github.com/coleam00/skills/tree/main/.claude/skills/piv-investigate-issue into .opencode/skills/piv-investigate-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "piv-investigate-issue", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
piv-investigate-issue- GitHub stars
- 676
- Token cost
- ~1.8k tokens
- SKILL.md length
- 488 words
- Files
- 1
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- MIT
At a glance
Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue).
- Works in 6 steps: Fetch GitHub Issue Details → Explore the Codebase — fan out in parallel → Review Recent History — when was it… → …
- Diagnose a bug/issue before fixing it
- SKILL.md covers Objective, Investigation Process, Output: Create RCA Document and Implementation Plan, plus 2 more sections
- Calls gh and git
What it does
Piv Investigate Issue is an agent skill from coleam00/skills. Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue). The investigate step before piv-implement-issue. Use to diagnose a bug/issue before fixing it.
Its SKILL.md is about 1.8k 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 Development, covering Root cause analysis. It works with GitHub. 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
- Diagnose a bug/issue before fixing it
- Tasks that involve Root cause analysis
Example prompts
- “/piv-investigate-issue”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
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 nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
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 Investigate Issue loads about 1.8k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 488 words of instructions outside code blocks.
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). 488 words, ~1,814 tokens.
Download SKILL.mdSave it as
.claude/skills/piv-investigate-issue/SKILL.md (or your agent's skills folder).- name
- piv-investigate-issue
- description
- Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue). The investigate step before piv-implement-issue. Use to diagnose a bug/issue before fixing it.
- argument-hint
- github-issue-id
Investigate Issue #$ARGUMENTS (Root-Cause Analysis)
Objective
Investigate GitHub issue #$ARGUMENTS from this repository, identify the root cause, and document findings for future implementation.
Prerequisites:
- Working in a local Git repository with GitHub origin
- GitHub CLI installed and authenticated (
gh auth status) - Valid GitHub issue ID from this repository
Investigation Process
1. Fetch GitHub Issue Details
Use GitHub CLI to retrieve issue information:
gh issue view $ARGUMENTSThis fetches:
- Issue title and description
- Reporter and creation date
- Labels and status
- Comments and discussion
2. Explore the Codebase — fan out in parallel
Dispatch specialized agents in parallel (one message, multiple Task calls) so exploration is fast and the noisy search stays out of your main context:
codebase-analyst— trace HOW the affected code works end-to-end: integration points, data flow, state/side effects, error handling. Return precisefile:linereferences, no suggestions.research-agent(a second explorer) — find WHERE the relevant code lives + patterns to mirror: the error strings from the issue, related functions/modules, similar implementations, existing test patterns.
Merge their findings into a short map (file:line + why each matters) before forming the root cause. (This is
the parallel-subagent fan-out, applied to diagnosis.)
3. Review Recent History — when was it introduced?
Check recent changes to the affected areas, and pin down when the bug entered:
!git log --oneline -20 -- [relevant-paths]
git blame -L <start>,<end> <affected-file> # who/when introduced the suspect linesDecide: a recent regression vs a long-standing bug vs original behavior — it changes both the fix and the risk.
4. Investigate Root Cause — the 5 Whys, with evidence
Don't stop at the symptom. Chain why → because until you reach the specific, fixable code, and back every link
with file:line evidence:
WHY does <symptom> happen? → because <cause A> (evidence: file.ts:123 — <snippet>)
WHY <cause A>? → because <cause B> (evidence: file.ts:456 — <snippet>)
… ROOT CAUSE: <the exact code/logic to change> (evidence: file.ts:789 — <snippet>)Watch for: input-validation gaps, unhandled edge cases, race/timing issues, wrong assumptions, missing error handling, integration mismatches.
5. Assess Impact
Determine:
- How widespread is this issue?
- What features are affected?
- Are there workarounds?
- What is the severity?
- Could this cause data corruption or security issues?
Show full SKILL.md (185 more words)Show less
6. Propose Fix Approach
Design the solution:
- What needs to be changed?
- Which files will be modified?
- What is the fix strategy?
- Are there alternative approaches?
- What testing is needed?
- Are there any risks or side effects?
Output: Create RCA Document
Save analysis as: docs/issues/issue-$ARGUMENTS.md
Required RCA Document Structure
# Root Cause Analysis: GitHub Issue #$ARGUMENTS
## Issue Summary
- **GitHub Issue ID**: #$ARGUMENTS
- **Issue URL**: [Link to GitHub issue]
- **Title**: [Issue title from GitHub]
- **Reporter**: [GitHub username]
- **Status**: [Current GitHub issue status]
## Assessment
Each value needs a one-line reason grounded in the investigation (not a guess):
| Metric | Value | Reasoning |
|--------|-------|-----------|
| Severity | Critical/High/Medium/Low | user impact · workaround · scope of failure |
| Complexity | Low/Medium/High | files touched · integration points · risk |
| Confidence | High/Medium/Low | evidence quality · unknowns · assumptions |
> **Confidence is the human-attention signal:** LOW confidence = a human should look before the fix runs. Say it honestly.
## Problem Description
[Clear description of the issue]
**Expected Behavior:**
[What should happen]
**Actual Behavior:**
[What actually happens]
**Symptoms:**
- [List observable symptoms]
## Reproduction
**Steps to Reproduce:**
1. [Step 1]
2. [Step 2]
3. [Observe issue]
**Reproduction Verified:** [Yes/No]
## Root Cause
### Affected Components
- **Files**: [List of affected files with paths]
- **Functions/Classes**: [Specific code locations]
- **Dependencies**: [Any external deps involved]
### Analysis
[Detailed explanation of the root cause]
**Evidence Chain (5 Whys):**WHY <symptom> → because <cause> (evidence: file:line — snippet)
… ROOT CAUSE: <the exact fixable thing> (evidence: file:line — snippet)
**Why This Occurs:**
[Explanation of the underlying issue]
**Code Location:**[File path:line number] [Relevant code snippet showing the issue]
### Related Issues
- [Any related issues or patterns]
## Impact Assessment
**Scope:**
- [How widespread is this?]
**Affected Features:**
- [List affected features]
**Severity Justification:**
[Why this severity level]
**Data/Security Concerns:**
[Any data corruption or security implications]
## Proposed Fix
### Fix Strategy
[High-level approach to fixing]
### Files to Modify
1. **[file-path]**
- Changes: [What needs to change]
- Reason: [Why this change fixes it]
2. **[file-path]**
- Changes: [What needs to change]
- Reason: [Why this change fixes it]
### Alternative Approaches
[Other possible solutions and why the proposed approach is better]
### Risks and Considerations
- [Any risks with this fix]
- [Side effects to watch for]
- [Breaking changes if any]
### Testing Requirements
**Test Cases Needed:**
1. [Test case 1 - verify fix works]
2. [Test case 2 - verify no regression]
3. [Test case 3 - edge cases]
**Validation Commands:**
```bash
[Exact commands to verify fix]Implementation Plan
[Brief overview of implementation steps]
This RCA document should be used by the piv-implement-issue skill.
Next Steps
- Review this RCA document
- Run the
piv-implement-issueskill with issue #$ARGUMENTS to implement the fix - Run the
piv-commitskill after implementation complete
## Post the summary to the issue
After writing the doc, post a short version as a GitHub comment — an audit trail, and so the fix can be
triggered/tracked from the issue itself:
```bash
gh issue comment $ARGUMENTS --body "<title · the Assessment table (severity/complexity/confidence + one-line reasons) · root cause in 1–2 lines · files to change · next: /piv-implement-issue $ARGUMENTS>"Edge cases
- Already closed → report it; still write the RCA if analysis is wanted.
- Already has a linked PR → warn; confirm before continuing.
- Can't pin the root cause → set Confidence: LOW, document the best hypothesis + what's uncertain, and flag it for a human before any fix.
- Scope too large → suggest splitting into smaller issues; focus this RCA on the core problem and list the rest as out-of-scope.
© 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-investigate-issue of coleam00/skills.
Open the folder on GitHubat commit 847be08
Compare with similar skills
Piv Investigate 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Piv Investigate Issue this skillcoleam00/skills | 676 | — | ~1.8k | Automated safety check: Pass | MIT | |
| OpenROAD Bug FixerThe-OpenROAD-Project/OpenROAD | 3.2k | — | ~784 | Automated safety check: Pass | BSD-3-Clause | |
| Octocode Code Researchbgauryy/octocode | 949 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Triagebot Action Bug Triagewithastro/astro | 63k | — | ~639 | Automated safety check: Pass | Custom licence | |
| CI TriageMentra-Community/MentraOS | 2.4k | — | ~582 | Automated safety check: Pass | Apache-2.0 | |
| Stereopy Issue ResponderSTOmics/Stereopy | 293 | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
Octocode Code Research
bgauryy/octocode
Researches code with evidence: traces callers, imports and cross-repo links, diagnoses failures and reports findings with exact file and line references and a confidence label.
- Official
Triagebot Action Bug Triage
withastro/astro
Takes a bug report for the triagebot-action GitHub Action through reproduction, root-cause diagnosis, an intended-behavior check and a fix attempt.
CI Triage
Mentra-Community/MentraOS
Triage failing GitHub PR checks: list failures with gh, fetch capped Actions logs, skip non-Actions checks, and summarize root cause.
Stereopy Issue Responder
STOmics/Stereopy
Generates professional maintainer-grade responses for Stereopy GitHub issues.
- Official
Reviewing Pull Requests
Shopify/shopify-app-js
Reviews pull requests for Shopify/shopify-app-js with comprehensive analysis including semver compliance (MAJOR/MINOR/PATCH classification), single responsibility validation, pattern consistency…
More from coleam00/skills
All 34 skills in this repoAblate 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…
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…
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.
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.
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…
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…
Related
Works with
Categories
Questions about Piv Investigate Issue
What does Piv Investigate Issue do?
Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue). Piv Investigate Issue is an agent skill from coleam00/skills. Investigate a GitHub issue — fan out parallel exploration, find the root cause (5 Whys, evidence-backed), and write a reviewable RCA artifact (then post a summary to the issue).
When should I use Piv Investigate Issue?
Piv Investigate Issue fits situations like: diagnose a bug/issue before fixing it; tasks that involve Root cause analysis.
How do I install Piv Investigate Issue in Claude Code?
Run `npx skills add coleam00/skills --skill piv-investigate-issue -a claude-code`. Or copy the skill folder (.claude/skills/piv-investigate-issue in coleam00/skills) into .claude/skills/piv-investigate-issue in your project. Claude Code loads it when a task matches its description.
How do I install Piv Investigate Issue in Codex?
Run `npx skills add coleam00/skills --skill piv-investigate-issue -a codex`. Or copy the skill folder (.claude/skills/piv-investigate-issue in coleam00/skills) into .agents/skills/piv-investigate-issue in your project. Codex loads it when a task matches its description.
Can I use Piv Investigate 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-investigate-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-investigate-issue, .gemini/skills/piv-investigate-issue, .github/skills/piv-investigate-issue and .opencode/skills/piv-investigate-issue in your project.
What does Piv Investigate Issue need to run?
Going by SKILL.md and its folder, Piv Investigate Issue needs the command-line tools its instructions call (gh and git).
Does Piv Investigate 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 Investigate 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 Investigate Issue use?
Piv Investigate 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 Investigate Issue use?
About 1.8k tokens (SKILL.md is roughly 7.3k 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 Investigate Issue?
Skills that share tags, products or a category with Piv Investigate Issue: OpenROAD Bug Fixer (The-OpenROAD-Project/OpenROAD, 3.2k stars), Octocode Code Research (bgauryy/octocode, 949 stars), Triagebot Action Bug Triage (withastro/astro, 63k stars) and CI Triage (Mentra-Community/MentraOS, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Piv Investigate Issue?
coleam00 (a GitHub user) maintains it in coleam00/skills, which has 676 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.