メニュー
Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Review recent code changes and broad codebase areas for critical and high severity security vulnerabilities. Use when Codex needs to clear `./out-security-review`, select 25 non-doc, non-test files split across past-day commits, past-week commits, and broad codebase coverage, group them into 6-8 review buckets, spawn one security-review sub-agent per review bucket, persist each candidate finding to `./out-security-review/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for responsible disclosure.
Record a short Playwright-based product demo video for significant UI or user-visible functionality changes. Use when Codex needs to show a workflow in motion for a PR, either by recording an existing targeted E2E spec or by creating a disposable one-off Playwright spec that captures the changed behavior in under a minute, then uploading the final video to Vercel Blob and preparing a PR comment body that says "Demo at commit {hash}" with a 1-2 sentence summary and durable hosted link.
Review the last 7 days of recent commits for large architecture improvements that dramatically improve maintainability. Use when the agent needs to clear `./out-code-architect`, select 25 non-doc, non-test files from recent commits across different parts of the repo, spawn one architecture-review sub-agent per starting file, persist each candidate finding to `./out-code-architect/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for issue filing.
Review the last 7 days of recent commits for critical and high severity bugs that break user experience. Use when the agent needs to clear `./out-bug-finder`, select 25 non-doc, non-test files from recent commits across different parts of the repo, spawn one bug-review sub-agent per starting file, persist each candidate finding to `./out-bug-finder/<starting_filename>_<timestamp>.md` using a filename-safe UTC ISO 8601 basic timestamp like `20260331T214512Z`, re-verify every candidate with fresh sub-agents, and emit final confirmed findings for issue filing.
Review recent GitHub Actions workflow runs, separate expected noise from actionable failures, and write a machine-readable workflow health report for deterministic post-agent issue handling.
Print the full host-side `scripts/pr.sh` command needed to create or switch to a feature branch, commit current changes, push, and open or update a PR outside the Docker sandbox using explicit flag-style inputs.
| name | keppo:pr-fix |
| description | Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks. |
Address all outstanding issues on a GitHub Pull Request by handling both review comments and failing CI checks.
$ARGUMENTS: Optional PR number or URL. If not provided, uses the current branch's PR.You MUST use the TaskCreate and TaskUpdate tools to track your progress. At the start, create tasks for each step below. Mark each task as in_progress when you start it and completed when you finish. This ensures you complete ALL steps.
When making decisions about review comments, consult docs/rules/product-principles.md. Use these principles to resolve ambiguous or subjective feedback autonomously. Only flag issues for human attention when the product principles do not provide enough guidance to make a decision.
This is a meta-skill that orchestrates sub-skills to comprehensively fix PR issues.
Rebase onto the base branch:
git fetch --allgh pr view --json baseRefName --jq '.baseRefName'git remote get-url upstream succeeds, use upstream/<base>, otherwise use origin/<base>git rebase <remote>/<base>git add <file>, git rebase --continue — repeat until completeRun /keppo:pr-fix:comments to handle all unresolved review comments:
Run /keppo:pr-fix:actions to handle failing CI checks:
Run /pr-push to commit and push all changes:
Post Summary Comment:
After both sub-skills complete, post a comment on the PR with a consolidated summary using gh pr comment. The comment should include:
<details> tags to collapse verbose details (e.g., full error messages, lengthy explanations)Error handling: If gh pr comment fails (e.g., due to network issues, rate limits, or permissions), log a warning but do not fail the entire skill if the underlying fixes were successful. The comment is informational and should not block a successful run.
Example formats:
Success:
## Claude Code completed successfully
### Summary
- Fixed 2 review comments
- Resolved 1 CI failure (lint error in `src/foo.ts`)
<details>
<summary>Details</summary>
... detailed information here ...
</details>
---
[Workflow run](https://github.com/keppoai/keppo/actions/runs/12345678)
Failure:
## Claude Code failed
### Summary
- Attempted to fix 2 review comments
- Failed to resolve 1 CI failure (lint error in `src/foo.ts`)
<details>
<summary>Error Details</summary>
**Error:** `lint` command failed with exit code 1.
```
... linter output ...
```
</details>
---
[Workflow run](https://github.com/keppoai/keppo/actions/runs/12345678)
Note: Include a link to the workflow run at the end. If the GITHUB_REPOSITORY and GITHUB_RUN_ID environment variables are available, use them to construct the URL: https://github.com/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID. If these environment variables are not set, omit the workflow run link.