القائمة
Use when updating GitHub PR title or body. Works around the gh pr edit GraphQL bug caused by GitHub's Projects Classic deprecation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when asked to review a local diff, a GitHub PR, or a whole codebase. Reports each finding with severity, likelihood, a worth-fixing verdict, and a high-level fix.
Use when asked to trim, clean up, shorten, or remove code comments. Two levels — "normal" (default) shortens verbose comments; "aggressive" deletes nearly every comment, keeping only trimmed unusual-workaround notes.
Use after generating or editing ASCII art, box diagrams, tables, or any monospace text art to ensure all lines, corners, and boxes are properly aligned.
Use when creating a new agent skill. Ensures the skill follows quality guidelines for SKILL.md files.
Use when the user wants to interact with Linear.app — reading or searching issues/tickets.
Use when writing or editing a system prompt for any LLM API or SDK (any code passing a `system=` / `system` role parameter, or a `.txt`/`.md` file holding such a prompt). Applies prompt-engineering and prompt-caching best practices.
| name | gh-update-pr |
| description | Use when updating GitHub PR title or body. Works around the gh pr edit GraphQL bug caused by GitHub's Projects Classic deprecation. |
| user-invocable | true |
| argument-hint | [<PR#>] |
gh pr edit is broken due to GitHub deprecating Projects Classic (projectCards GraphQL field error). Use the REST API instead. gh pr view and gh pr create still work fine — only gh pr edit is affected.
gh pr edit to update PR title or body. It will fail with a GraphQL error.gh api with the REST endpoint. Always pipe JSON via jq --arg to avoid shell injection:
jq -n --arg title "..." --arg body "..." '{title: $title, body: $body}' | \
gh api repos/{owner}/{repo}/pulls/{number} -X PATCH --input - --jq '.html_url'
gh pr view --json number,url,baseRefName
body in the JSON payload, and vice versa. Including an unchanged field risks overwriting it with stale content.html_url (not an error).gh pr view --json title,body and verify the updated fields match what was intended.gh pr view needs repo context. If it fails, pass --repo owner/repo explicitly.gh pr view first — do not hardcode or assume them.