CtrlK
BlogDocsLog inGet started
Tessl Logo

prp-issue

Investigate a GitHub issue and implement the fix - analyze codebase, create a plan, then code, PR, and self-review. Use when the user wants to investigate or triage a GitHub issue or bug report, fix an investigated issue, implement an issue fix, or invokes /prp-issue.

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/prp-issue/SKILL.md
SKILL.md
Quality
Evals
Security

PRP Issue

Input: $ARGUMENTS

# --- PRP store resolver (canonical; keep byte-identical across skills) ---
_gd="$(git rev-parse --path-format=absolute --git-common-dir 2>/dev/null)"
case "$_gd" in */.git) _root="${_gd%/.git}" ;; "") _root="$PWD" ;; *) _root="$_gd" ;; esac
_root="$(cd "$_root" && pwd -P)"
_name="$(basename "$_root" | tr '[:upper:]' '[:lower:]' | tr -cs 'a-z0-9' '-' | sed 's/^-*//;s/-*$//')"
PRP_DIR="${PRP_HOME:-$HOME/.prp}/${_name:-project}-$(printf %s "$_root" | git hash-object --stdin | cut -c1-8)"
mkdir -p "$PRP_DIR"; [ -f "$PRP_DIR/project.json" ] || printf '{"path": "%s", "name": "%s"}\n' "$_root" "${_name:-project}" > "$PRP_DIR/project.json"

Two-phase issue workflow: investigate an issue into an implementation artifact, then fix it from that artifact (code, PR, self-review).

Route on the verb

Read the first token of $ARGUMENTS to choose the workflow. Everything after the verb is the issue/artifact argument the workflow operates on.

First tokenWorkflowOperates on
investigateworkflows/investigate.mdissue number / URL / free-form description
fixworkflows/fix.mdissue number / artifact path (+ optional --base <branch>)
no verb (a bare issue number, URL, or description)workflows/investigate.mdthe whole argument — investigation is the entry point; you investigate before you fix

Action: strip the leading verb (if present), then follow the matching workflow file end-to-end. Do not blend the two — pick one and execute it fully.

Notes

  • investigate is read-mostly: it analyzes, writes an artifact under $PRP_DIR/issues/, and (for GitHub issues) posts a comment.
  • fix is side-effecting: it creates a branch, commits, opens a PR, and posts a self-review. Only run it once an investigation artifact exists.
  • Typical flow: prp-issue investigate <number> → review the artifact → prp-issue fix <number>.
Repository
Wirasm/prp
Path

.claude/skills/prp-issue/SKILL.md

Commit

1142738

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.

Claim skill