Menu
Update a pull request description. Use when asked to update PR description, edit PR body, or refresh PR details.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Keep the Threa Pi remote-control extension in `extensions/pi-remote/` aligned with the current Pi extension API and Threa bot-runtime public API. Use when asked to update, verify, sync, or troubleshoot the Pi remote plugin, `/remote-control`, or `threa-remote.ts`.
Create a well-structured pull request with proper description, design decisions, and file changes. Use when asked to create a PR, open a PR, or submit changes for review.
Call Threa's public REST API (send/list/search/update/delete messages, list streams/users/members, search memos/attachments) with curl or a Bun script. Use when asked to post messages to a stream, seed a stream with test data, drive the API from automation, dedupe by metadata, inspect a production workspace (streams, messages, members) for troubleshooting, or otherwise hit https://staging.threa.io / https://app.threa.io endpoints with an API key. Reads from production should use the read-only prod key.
Rewrite user-facing copy (marketing pages, docs, headings, UI microcopy, READMEs, PR descriptions) to strip AI-slop and salesy tone, leaving plain, understated, factual prose. Use when asked to "deslopify", "deslop", "remove the AI slop", "make this less salesy/less AI-sounding", "make the copy plainer", or when reviewing copy for slop tells.
Run multi-perspective code review on a PR or the local branch
Write a session handover doc for the next agent picking up this line of work. Use when asked to "write a handover", "hand over", "handoff doc", or at the end of a session whose work continues in a future session.
| name | update-pr |
| description | Update a pull request description. Use when asked to update PR description, edit PR body, or refresh PR details. |
Update an existing PR's description, working around sandbox heredoc limitations.
# View current PR (assumes on feature branch)
gh pr view --json number,title,body
# Or specify PR number
gh pr view 123 --json number,title,body
Use printf to avoid heredoc issues:
printf '%s\n' \
'## Problem' \
'' \
'Description of the problem...' \
'' \
'## Solution' \
'' \
'Description of the solution...' \
> /tmp/claude/pr-body.md
For longer content, build it incrementally:
# Start fresh
> /tmp/claude/pr-body.md
# Add sections
printf '%s\n' '## Problem' '' >> /tmp/claude/pr-body.md
printf '%s\n' 'The issue is...' '' >> /tmp/claude/pr-body.md
printf '%s\n' '## Solution' '' >> /tmp/claude/pr-body.md
printf '%s\n' 'We fixed it by...' >> /tmp/claude/pr-body.md
# Using body-file (may show GraphQL warning but still works)
gh pr edit 123 --body-file /tmp/claude/pr-body.md
# If that fails, use the API directly
gh api repos/{owner}/{repo}/pulls/123 --method PATCH \
-f body="$(cat /tmp/claude/pr-body.md)"
gh pr view 123 --json body -q '.body' | head -20
rm /tmp/claude/pr-body.md
GraphQL Projects (classic) warning:
This warning appears but the update usually still succeeds. Verify with gh pr view.
Heredoc fails: Expected in sandbox mode. Use printf approach.
Body too long for single printf: Build the file incrementally with append (>>).
Special characters:
Use single quotes. For apostrophes: 'Don'\''t'
Follow this template for consistency. The prose is the high-level summary; the full
implementation plan stays collapsed in the <details> block at the end (branch plans
are never committed — .claude/plans/ is gitignored).
## Problem
[What issue exists?]
## Solution
[High-level approach]
### Key design decisions
**1. [Decision]**
[Explanation]
## Files changed
| File | Change |
| -------------- | ----------- |
| `path/file.ts` | Description |
## Test plan
- [ ] Test item
<details>
<summary>📋 Full implementation plan</summary>
[Full plan. Use `/sync-plan` to compose/refresh it.]
</details>
---
🤖 _PR by [Claude Code](https://claude.com/claude-code)_
Preserve the plan block when editing. If the current body already has a
<summary>📋 Full implementation plan</summary> block, keep it (or refresh it with
/sync-plan) — don't drop it when you rewrite the prose sections. To regenerate the plan
content itself, prefer /sync-plan, which locates and replaces the block in place.
Quick body update:
printf '%s\n' '## Problem' '' 'Users cannot login' '' '## Solution' '' 'Fixed auth token validation' '' '---' '🤖 _PR by [Claude Code](https://claude.com/claude-code)_' > /tmp/claude/pr-body.md
gh pr edit 123 --body-file /tmp/claude/pr-body.md
Using API fallback:
gh api repos/myorg/myrepo/pulls/123 --method PATCH \
-f body="$(cat /tmp/claude/pr-body.md)"