Menú
This skill should be used when the user asks to "update the PR", "update PR body", "update PR title", "sync PR description", "update pull request", or wants the pull request title and body to reflect the actual changes on the current branch.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when the user asks to implement a feature, add functionality, or build something new.
This skill should be used when the user asks to "open a browser", "navigate to a URL", "test the UI", "check a page", "browse a website", "take a screenshot", "fill a form", "click a button", or any browser automation task. Also triggered by CLAUDE.md directives like "Use 'agent-browser' when navigating".
FastAPI engineering choices. To be used when asked to "create router", "create crud router", "add new endpoint" or similar in a fastapi codebase.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
This skill should be used when the user asks to "investigate something incrementally", "start a discovery journal", "journal my findings", "explore this step by step and write it down", "create a research journal", or wants to build understanding of a problem through guided, step-by-step investigation with findings persisted to a journal file.
Knowledge on how to work with Github projects. To be used when asked to "create a task in github project" or "add ticket to gh project" or similar.
| name | update-pr |
| description | This skill should be used when the user asks to "update the PR", "update PR body", "update PR title", "sync PR description", "update pull request", or wants the pull request title and body to reflect the actual changes on the current branch. |
Analyze the current branch's changes and update the associated pull request's title and body to accurately reflect what was done.
gh pr view and gh pr edit work without a PR number when on the associated branch)gh CLI is authenticatedRun these commands in parallel to understand the current state:
gh pr view --json number,title,body,headRefName,baseRefName
gh pr diff
git log <baseRefName>..HEAD --oneline
Use baseRefName from the PR view output as the base branch for the log and diff commands.
Review ALL commits and the full diff, not just the latest commit. Identify:
Title rules:
Body format:
## Summary
- <bullet points describing changes>
## Test plan
- [ ] <verification steps>
---
> Drafted by <your name> 🤖
Keep bullet points concise. The summary should focus on "why" not "what" when possible. Test plan items should be actionable verification steps.
Show the drafted title and body to the user. Wait for explicit approval before applying.
Use the REST API directly to avoid a known GraphQL error where gh pr edit fails because it queries the deprecated "Projects (classic)" projectCards field:
gh api repos/<owner>/<repo>/pulls/<number> -X PATCH -f title="<title>" -f body="$(cat <<'EOF'
<body>
EOF
)" --jq '.html_url'
Always use a HEREDOC for the body to preserve formatting. Extract owner/repo from gh repo view --json nameWithOwner --jq .nameWithOwner.
After applying, return the PR URL from the output.