update-tracking
Update a tracking PR with current sub-issue status and progress
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Update a tracking PR with current sub-issue status and progress
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Automatically implement all sub-issues of an epic in dependency order
Implement a GitHub issue with automated PR creation
End-of-session retrospective. Captures knowledge from any working session (debug, implementation, config, deployment) as reusable scripts, CLAUDE.md procedures, or skill proposals. Run before ending a session to prevent knowledge loss.
Decompose a large GitHub issue into sub-issues and create a tracking draft PR
OWASP-guided security code review for a specific domain or issue
Project kickoff checklist based on lessons learned from previous projects. Generates a tailored checklist and optionally creates GitHub issues.
| name | update-tracking |
| description | Update a tracking PR with current sub-issue status and progress |
| argument-hint | <pr-number> |
| user-invocable | true |
Update a tracking/parent PR with the current status of all linked sub-issues.
The user provides a PR number: $ARGUMENTS
~/.claude/bin/gh-save.sh /tmp/pr-$ARGUMENTS.json pr view $ARGUMENTS --json number,title,body,state
Use the Read tool to read /tmp/pr-$ARGUMENTS.json and extract:
Fetch all sub-issue statuses in one batch (outputs a JSON array):
~/.claude/bin/batch-issue-status.sh <repo> [sub-issue-numbers...]
Also check merged and open PRs for all sub-issues in one batch:
~/.claude/bin/batch-pr-for-issues.sh <repo> [sub-issue-numbers...]
Map states to status indicators:
completed = count of ✅ items
total = count of all sub-issues
percentage = (completed / total) * 100
Format: **Progress:** X of Y sub-issues complete (Z%)
If 100%: **Progress:** Y of Y sub-issues complete (100%)! 🎉
Replace the sub-issues table section with updated status:
### Sub-Issues
| # | Sub-Issue | Status | PR |
|---|-----------|--------|-----|
| 1 | #123 - Foundation setup | ✅ Complete | PR #125 merged |
| 2 | #124 - Core feature | 🔄 In Progress | PR #130 |
| 3 | #125 - Integration | ⏳ Pending | - |
**Progress:** 1 of 3 sub-issues complete (33%)
Display the changes to the user:
## PR #[number] Update Preview
### Changes:
- Sub-issue #123: ⏳ Pending → ✅ Complete (PR #125 merged)
- Sub-issue #124: ⏳ Pending → 🔄 In Progress (PR #130)
- Progress: 0% → 33%
Apply this update? (y/n)
Only after user confirmation. Write the updated body to a temp file first, then use --body-file to avoid long inline arguments:
# Write updated body to temp file using the Write tool
# Then apply it:
gh pr edit $ARGUMENTS --body-file /tmp/pr_body.md
| Emoji | Meaning | Condition |
|---|---|---|
| ⏳ | Pending | Issue open, no PR |
| 🔄 | In Progress | Issue open, has PR (draft or ready) |
| ✅ | Complete | Issue closed |
| ❌ | Blocked | Issue has "blocked" label |
| 🎉 | All Done | 100% complete (add to progress line) |
If sub-branches have been merged, update the branch structure section:
## Branch Structure
develop ↑ issue-689-admin-dashboard (this PR) ↑ issue-690-foundation (✅ merged) issue-691-home-page (✅ merged) issue-692-backend (🔄 in progress) issue-693-frontend (⏳ pending)
/update-tracking 696
This will: