القائمة
Update an existing GitHub PR description to reflect current changes after incorporating feedback
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Maintain the NeMo Data Designer Fern docs site under fern/. Use for any documentation change. Triggered by: "edit docs", "add doc page", "update docs", "rename page", "fix broken link", "add redirect", "preview docs", "publish docs", "regenerate notebooks", "update dev note", any request that touches `fern/`.
Perform a thorough code review of the current branch or a GitHub PR by number.
Search local Fern documentation for content related to a topic
Create a GitHub PR with a well-formatted description matching the repository PR template (flat Changes by default; optional Added/Changed/Removed/Fixed grouping)
Commit current changes with a clear, descriptive message
Search GitHub issues, discussions, and PRs for content related to a topic
| name | update-pr |
| description | Update an existing GitHub PR description to reflect current changes after incorporating feedback |
| argument-hint | ["special instructions"] |
| disable-model-invocation | true |
| metadata | {"internal":true} |
Update the description of an existing GitHub pull request for the current branch.
$ARGUMENTS can be used for:
--title flag: Include to also update the PR titlegh pr view --json number,title,body,url,headRefName,state
Important checks:
/create-pr insteadRun these commands in parallel to understand the full state:
git status --porcelaingit log origin/main..HEAD --onelinegit diff --stat origin/main..HEADgit diff origin/main..HEADgh repo view --json nameWithOwner -q '.nameWithOwner' (for constructing file URLs)Important checks:
Flag for special reviewer attention:
pyproject.toml, requirements.txt)Push any new commits (if needed):
git push
Generate updated description using the same template as create-pr (see below)
Update the PR body:
gh pr edit <number> --body "$(cat <<'EOF'
<body>
EOF
)"
Optionally update title (if --title flag was provided):
gh pr edit <number> --title "<new-title>"
Return the PR URL to the user.
Use the same template as create-pr, with an updated footer:
## Summary
[1-2 sentence overview of what this PR accomplishes]
## Changes
### Added
- [New features/files - link to key files when helpful]
### Changed
- [Modified functionality - reference commits for specific changes]
### Removed
- [Deleted items]
### Fixed
- [Bug fixes - if applicable]
## Attention Areas
> Reviewers: Please pay special attention to the following:
- [`path/to/critical/file.py`](https://github.com/<owner>/<repo>/blob/<branch>/path/to/critical/file.py) - [Why this needs attention]
---
*Description updated with AI*
[filename](https://github.com/<owner>/<repo>/blob/<branch>/path/to/file.py)[description](https://github.com/<owner>/<repo>/blob/<branch>/path/to/file.py#L42-L50)abc1234 - GitHub auto-links short commit SHAs in PR descriptions/create-pr instead/create-pr| Aspect | /create-pr | /update-pr |
|---|---|---|
| PR state | Creates new | Updates existing |
| Command | gh pr create | gh pr edit |
| First step | Check for commits | Find existing PR |
| Branch push | With -u flag | Simple push |
| Title | Always sets | Optional (with --title) |
| Footer | "Generated with AI" | "Description updated with AI" |