メニュー
Generate a two-week status update from PRs. Use when the user wants a summary of their work for the last two weeks. The user must specify the repository (owner/repo).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | weekly-update |
| description | Generate a two-week status update from PRs. Use when the user wants a summary of their work for the last two weeks. The user must specify the repository (owner/repo). |
Generates a concise two-week update from merged and in-progress PRs for a given repository.
The user must provide the target repository as owner/repo (e.g. acme/backend). If not provided, ask for it.
Resolve the User
gh api user -q '.login' to get the GitHub usernameCalculate the Two-Week Range
current_day=$(date +%u) # 1=Monday, 7=Sunday
days_since_friday=$(( (current_day + 2) % 7 ))
range_end=$(date -v-"${days_since_friday}"d +%Y-%m-%d)
range_start=$(date -v-"$((days_since_friday + 13))"d +%Y-%m-%d)
Fetch Merged PRs
gh pr list --repo <owner/repo> --author <username> --state merged \
--search "merged:${range_start}..${range_end}" \
--json number,title,url,body,mergedAt --limit 100
Fetch Open PRs with Activity
gh pr list --repo <owner/repo> --author <username> --state open \
--json number,title,url,body,updatedAt --limit 50
Filter to PRs updated within the same two-week range.
Generate the Update
# Two Weeks: Jan 04 – Jan 17, 2026
## Merged
**Add user settings page** — [#1234](https://github.com/owner/repo/pull/1234)
- Implemented preferences form with validation
- Added dark mode toggle persistence
## In Progress
**Migrate to new API v3** — [#1240](https://github.com/owner/repo/pull/1240) (draft)
- Significant progress on endpoint migration, not yet merged
Create or refresh GitHub pull requests with direct gh commands. Use when opening a PR, updating an existing PR after material changes, or drafting a PR title/body.
Implement a provided spec while maintaining a running implementation-notes.md file. Use when the user asks to implement a spec, plan, ticket, or requirements document and wants ongoing notes about design decisions, deviations, tradeoffs, or open questions.
Fix CI failures. Use when the user wants to fix failing CI checks, GitHub Actions, or pipeline errors. Automatically checks CI status, fixes issues, commits, pushes, and waits for results. Asks for input when fixes are unclear.
Sync current branch with main. Use when the user wants to update their feature branch with the latest changes from the main branch. Fetches, rebases, and handles conflicts.