菜单
Update an existing PR's title and description by scanning project rules for conventions and the PR template, synthesizing both from the delta between the branch and target, then applying changes via 'gh api' (gh pr edit fails in this repo).
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | update-pr |
| description | Update an existing PR's title and description by scanning project rules for conventions and the PR template, synthesizing both from the delta between the branch and target, then applying changes via 'gh api' (gh pr edit fails in this repo). |
| license | BSD 3-Clause |
| compatibility | Requires gh CLI authenticated with a repo that has .github/PULL_REQUEST_TEMPLATE.md. |
| metadata | {"version":"1.0","agent":"coding"} |
Update an existing pull request's title and description following project conventions.
Identify the PR
The PR number is provided in the chain context (the text after /update-pr). If no PR number is provided, report an error and stop — this skill requires a specific PR to update.
Confirm the PR exists:
gh pr view <PR_NUMBER> --json title,state,url --repo avoidwork/madz
Scan Project Rules
Scan the project root and any specified paths for a .agent rules file and read its contents:
# Scan the project root for AGENTS.md or similar rules file
Extract:
.github/PULL_REQUEST_TEMPLATE.md if it exists)Read the PR template
cat .github/PULL_REQUEST_TEMPLATE.md
If the file doesn't exist, construct a reasonable description with: Description, Type of Change, Testing, Coverage, Checklist.
Gather the full delta
You must collect the complete picture — every commit and every file change between the branch and its target. Do not rely on the most recent commit alone.
# Get all commits on the branch (oldest first)
git log --reverse <base>..<head> --oneline --no-decorate
# Get the full diff stats (files changed, lines added/removed)
git diff <base>..<head> --stat
# Get the full diff (for detailed change analysis) — NOTE: On large branches, this may produce very large output.
# If output exceeds ~50,000 characters, use --stat only and note "Large delta — full diff truncated."
git diff <base>..<head>
Replace <base> with the PR's base branch (usually main) and <head> with the branch's HEAD commit. Use gh pr view <number> --json baseRefName,headRefName to get these values if unsure.
From this data, identify:
Draft the title
Synthesize the title from the complete delta — all commits and all file changes. Follow Conventional Commits format: <type>: <short description>
Type selection priority (use the highest-priority type present in the delta):
fix: — if any commit fixes a bugfeat: — if any commit adds a featuredocs: — if only documentation/spec changestest: — if only test changesrefactor: — if only refactoring with no behavior changechore: — if only maintenance tasksDescription selection:
Examples:
fix: resolve agent stalling on empty conversation historyfeat: add cron-based auto-reflection schedulingdocs: add compliance framework and borderline escalation rules to safety guidelinesDraft the description
Synthesize the description from the complete delta — all commits and all file changes. Fill out every section of the PR template. Never leave a section blank — use N/A if not applicable.
Description body:
Template sections:
Apply via gh api
Never use gh pr edit — it fails in this repo. Use the GitHub API instead:
# Determine repo from git remote
REPO=$(git remote get-url origin | sed 's/.*:\(.*\)\.git$/\1/' | sed 's/.*\///')
OWNER=$(echo "$REPO" | cut -d'/' -f1)
PROJECT=$(echo "$REPO" | cut -d'/' -f2)
gh api "repos/$OWNER/$PROJECT/pulls/<PR_NUMBER>" \
-f title="<DRAFTED_TITLE>" \
-f body="<DRAFTED_BODY>"
Handle API errors: If the API call returns a non-200 status, report the error and stop. Common errors:
Coverage verification: The skill instructs to "Confirm 100% line coverage maintained" but there's no way to verify this without running tests. If code changes were made, run npm run coverage and check the output. If no code changes were made (docs-only, config-only), note "No code changes — coverage N/A."
Confirm
Show the user the updated PR URL and a summary of what changed.
gh api repos/avoidwork/madz/pulls/214 \
-f title="docs: rename OpenSpec change directory and archive core-architecture-spec" \
-f body="## Description\n\nRenamed the \`core-architecture-spec\` OpenSpec change...\n\n## Type of Change\n\n- [x] Documentation update\n- [x] Refactor (no functional changes)\n\n## Testing\n\nN/A — spec-only change, no code modified.\n\n## Coverage\n\n- [x] 100% line coverage maintained (no code changes)\n\n## Checklist\n\n- [x] \`npm run lint\` passes\n- [x] Tests pass with 100% line coverage\n- [x] No forbidden patterns used\n- [x] Conventional Commit style applied\n"
scanAgents before drafting — conventions may vary per projectN/Agh api, never gh pr editAudits each directory in ./src for bugs, security vulnerabilities, and performance issues sequentially. Generates one consolidated issue per directory via /create-issue.
Audits Agent Skills SKILL.md files against the protocol specification and best practices. Identifies issues across 10 categories: schema violations, naming, description quality, structure, progressive disclosure, file references, best practices, calibration, content quality, and optional directories. Produces a structured report with severity levels and actionable fixes.
Expert System Prompt Evaluator Agent. Analyzes, rates, and provides actionable feedback for system prompts against a 7-criteria framework. Returns structured machine-readable JSON output with weighted scores, evidence-based reasoning, and harness-aware recommendations.
Automates the complete git workflow: scans project rules for conventions, stages all changes, commits, pushes to the remote, and opens a Pull Request. Ensures strict compliance with documentation rules, including rule 5.4.
Orchestrates a full feature lifecycle: receive goals, synthesize detailed specs, propose via OpenSpec, commit & push, apply tasks, audit results, update PR, and post audit results as a comment.
Receives a user description, synthesizes it into a title and description, categorizes as 'fix' or 'feat', creates a GitHub issue, audits the codebase for actionable details, and updates the issue with findings.