TitanX: Skill for Claude Code

PR Review Fix Skill

Automated workflow to resolve all issues surfaced in a pr-review report — parse summary → detect PR status → create fix branch or checkout original branch → fix by priority → quality gate → commit → publish → verify.

Announce at start: "I'm using pr-fix skill to fix all review issues."

Usage

/pr-fix [pr_number]

pr_number is optional. The skill requires a pr-review report to be present in the current session.

---

Mode Detection

At the very start of execution, check $ARGUMENTS for the --automation flag:

# $ARGUMENTS example: "123 --automation" or "123"
AUTOMATION_MODE=false
if echo "$ARGUMENTS" | grep -q -- '--automation'; then
  AUTOMATION_MODE=true
fi

In automation mode:

• Skip all yes/no confirmation prompts — follow the default best path

---

Steps

Step 0 — Locate the Review Report

The pr-review skill must have been executed in the current session. The review report (containing a "汇总" table) must be present in the conversation.

If no review report is found in the current session, abort immediately with:

No pr-review report found in this session. Please run /pr-review <pr_number> first.

Extract the PR number from the report header:

## Code Review：<PR 标题> (#<PR_NUMBER>)

If pr_number is provided as an argument, use it to override the extracted number.

---

Step 1 — Parse the Summary Table

Locate the 汇总 section in the review report:

| #   | 严重级别    | 文件        | 问题 |
| --- | ----------- | ----------- | ---- |
| 1   | 🔴 CRITICAL | `file.ts:N` | ...  |

Build an ordered issue list, grouped by severity:

Priority	Severity	Emoji
1	CRITICAL	🔴
2	HIGH	🟠
3	MEDIUM	🟡
4	LOW	🔵

If the 汇总 table is empty, abort with:

No issues found in the review summary. Nothing to fix.

LOW issues: Skip — do not fix.

After filtering out LOW issues, if no CRITICAL / HIGH / MEDIUM issues remain, abort with: