원클릭으로
jikime-workflow-pr-lifecycle
PR lifecycle automation from creation to merge with CI monitoring and review resolution loops
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
PR lifecycle automation from creation to merge with CI monitoring and review resolution loops
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
AI-powered legacy site rebuilding workflow. Captures screenshots, analyzes source code, and generates modern frontend/backend code. Claude Code reads screenshots and writes actual code. Use when rebuilding legacy PHP, WordPress, or similar sites to Next.js, React, or other modern frameworks.
하네스를 구성합니다. 전문 에이전트를 정의하며, 해당 에이전트가 사용할 스킬을 생성하는 메타 스킬. (1) '하네스 구성해줘', '하네스 구축해줘' 요청 시, (2) '하네스 설계', '하네스 엔지니어링' 요청 시, (3) 새로운 도메인/프로젝트에 대한 하네스 기반 자동화 체계를 구축할 때, (4) 하네스 구성을 재구성하거나 확장할 때 사용.
Leader agent role guide for jikime team orchestration. Covers task distribution, plan approval, worker monitoring, and team shutdown. Use when spawned as the leader role in a jikime team.
Reviewer agent role guide for jikime team orchestration. Covers plan review, quality assessment, acceptance criteria validation, and feedback delivery via team inbox. Use when spawned as the reviewer role in a jikime team.
Use this skill when the user asks to "jikime team을 사용해줘", "팀 만들어줘", "에이전트 생성해줘", "멀티 에이전트로 작업해줘", "병렬로 에이전트 실행해줘", "여러 에이전트 조율해줘", "작업을 여러 에이전트에게 분배해줘", "team status 확인해줘", "task 만들어줘", "inbox 확인해줘", or mentions "jikime team", "multi-agent coordination", "spawn agents", "team tasks", "agent inbox", "task board", "team leader", "team worker". Also trigger when the scope of work is large enough to benefit from splitting into parallel subtasks — for example "전체 코드베이스 리팩토링", "여러 기능 동시에 구현", "대규모 분석", "full-stack app 만들어줘". Provides comprehensive guidance for using the jikime team CLI to orchestrate multi-agent teams with task management, messaging, and monitoring.
Claude Code skill for operating as part of a jikime multi-agent team (swarm). Provides command reference, coordination protocols, and role-specific workflows for leader, worker, and reviewer agents. Triggers when the task involves multi-agent coordination, spawning workers, assigning tasks, monitoring team progress, or when the scope exceeds what a single agent can efficiently handle (e.g., "build a full-stack app", "implement multiple features in parallel", "refactor the entire codebase"). Also triggers on keywords: "create a team", "spawn agents", "assign tasks", "team status", "board attach", "agent inbox", "multi-agent", "swarm", "jikime team".
| name | jikime-workflow-pr-lifecycle |
| description | PR lifecycle automation from creation to merge with CI monitoring and review resolution loops |
| version | 1.0.0 |
| tags | ["workflow","pr","ci","review","automation","github"] |
| triggers | {"keywords":["PR","pull request","create PR","merge","CI check","review comments"],"phases":["run","sync"],"agents":["manager-git","manager-quality"],"languages":[]} |
| progressive_disclosure | {"enabled":true,"level1_tokens":"~100","level2_tokens":"~2500"} |
| user-invocable | true |
| context | fork |
| agent | manager-git |
| allowed-tools | ["Read","Write","Edit","Bash","Grep","Glob","TodoWrite"] |
Automated PR creation, CI monitoring, review resolution, and merge workflow.
Automates the complete pull request lifecycle:
Before creating a PR, verify:
# Ensure all changes are committed
git status --porcelain
# Ensure branch is up to date with base
git fetch origin main
git diff origin/main...HEAD --stat
# Ensure build passes locally
npm run build # or equivalent
npm test # or equivalent
Use gh pr create with structured description:
gh pr create \
--title "feat(scope): concise description" \
--body "$(cat <<'EOF'
## Summary
- What this PR does (1-3 bullet points)
## Changes
- List of significant changes
- New files, modified files, deleted files
## Test Plan
- [ ] Unit tests pass
- [ ] Integration tests pass
- [ ] Manual testing completed
- [ ] Edge cases covered
## Screenshots (if UI changes)
N/A
EOF
)"
Follow conventional commits:
feat(scope): add user authentication
fix(scope): resolve memory leak in WebSocket
refactor(scope): extract validation logic
docs(scope): update API documentation
test(scope): add integration tests for auth
PR Created
↓
Check CI Status (gh pr checks)
├── All Passing → Proceed to Review
├── Pending → Wait 60s, re-check (max 10 min)
└── Failed → Diagnose and Fix
↓
Fix CI Failure
↓
Push Fix
↓
Re-check (max 5 retry cycles)
├── Pass → Proceed to Review
└── Still failing after 5 cycles → STOP, report to user
# Check CI status
gh pr checks
# Watch CI (blocking wait)
gh pr checks --watch --fail-fast
# Get specific check details
gh pr view --json statusCheckRollup --jq '.statusCheckRollup[]'
When CI fails:
gh pr checks outputgh run view <run-id> --log-failed| Category | Action | Example |
|---|---|---|
| Lint error | Auto-fix | npm run lint --fix |
| Type error | Fix types | Missing type annotation |
| Test failure | Fix test or code | Assertion mismatch |
| Build error | Fix build | Missing dependency |
| Flaky test | Re-run | gh run rerun <run-id> |
# Fix the issue
# ...
# Commit fix
git add -A
git commit -m "fix(ci): resolve [specific issue]"
git push
| Parameter | Default | Description |
|---|---|---|
| CI wait timeout | 10 min | Max time to wait for CI |
| CI retry cycles | 5 | Max fix-and-recheck attempts |
| Polling interval | 60s | Time between status checks |
If timeout reached:
CI monitoring timed out after 10 minutes.
Last status: 2/5 checks passed, 1 pending, 2 failed.
Failed checks:
- lint: ESLint found 3 errors
- test: 2 test failures in auth.test.ts
Action needed: Manual intervention required.
CI Passed
↓
Wait for Review
↓
Review Comments Received
├── Check comment count
├── Read all comments
├── Categorize and prioritize
├── Fix issues
├── Push fixes
├── Re-request review
└── Repeat (max 3 review cycles)
├── Approved → Merge
└── Still changes requested after 3 cycles → STOP, report
# List PR review comments
gh api repos/{owner}/{repo}/pulls/{pr-number}/comments \
--jq '.[] | {path: .path, line: .line, body: .body}'
# List PR reviews
gh pr view --json reviews --jq '.reviews[] | {state: .state, body: .body}'
# Check if approved
gh pr view --json reviewDecision --jq '.reviewDecision'
| Type | Priority | Action |
|---|---|---|
| Bug/Logic error | Critical | Fix immediately |
| Style/Convention | Medium | Apply suggestion |
| Suggestion/Optional | Low | Evaluate, respond |
| Question | Low | Answer in comment |
| Nitpick | Low | Apply if trivial |
git add -A
git commit -m "fix(review): address review comments
- Fix [issue 1]
- Apply [suggestion 2]
- Respond to [question 3]"
git push
gh:gh pr comment --body "Addressed all review comments. Please re-review."
| Parameter | Default | Description |
|---|---|---|
| Review cycles | 3 | Max rounds of review resolution |
| Review wait | Manual | User notified to wait for review |
- [ ] CI checks all passing
- [ ] Review approved (no changes requested)
- [ ] No merge conflicts
- [ ] Branch is up to date with base
# Check merge readiness
gh pr view --json mergeable --jq '.mergeable'
# Merge (squash recommended)
gh pr merge --squash --delete-branch
# Or merge commit
gh pr merge --merge --delete-branch
# Switch back to main
git checkout main
git pull
# Clean up local branch
git branch -d feature-branch
1. Pre-PR checks (build, test, lint)
2. gh pr create with structured body
3. CI Monitoring Loop:
- gh pr checks --watch (wait up to 10 min)
- If failed: diagnose → fix → push → re-check (max 5 cycles)
4. Review Resolution Loop:
- Read comments via gh api
- Fix issues → push → re-request (max 3 cycles)
5. Final validation
6. gh pr merge --squash --delete-branch
7. Post-merge cleanup
## J.A.R.V.I.S.: PR Lifecycle - Created
PR #42 created: feat(auth): add user authentication
URL: https://github.com/owner/repo/pull/42
Monitoring CI checks...
## J.A.R.V.I.S.: PR Lifecycle - CI Passed
All 5/5 CI checks passed:
- lint: passed
- type-check: passed
- test: passed (87% coverage)
- build: passed
- security: passed
Waiting for review...
## J.A.R.V.I.S.: PR Lifecycle - Review Resolved
Addressed 4 review comments in 1 cycle:
- 2 bug fixes applied
- 1 style suggestion applied
- 1 question answered
Re-requested review. CI re-running...
## J.A.R.V.I.S.: PR Lifecycle - Complete
PR #42 merged successfully (squash).
Branch feature/auth deleted.
<jikime>DONE</jikime>
| Skill | Relationship |
|---|---|
jikime-workflow-poc | Phase 5 uses this skill |
jikime-workflow-task-format | PR tasks use 5-field format |
jikime-workflow-loop | CI fix loop similar to Ralph Loop |
Version: 1.0.0 Last Updated: 2026-02-27 Source: Adapted from smart-ralph PR lifecycle automation