메뉴
Review and validate Renovate dependency PRs. Assesses risk, runs tests, fixes simple issues, and recommends merge/close/hold. Use when reviewing PRs from Renovate bot.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Design or edit a Mediforce WorkflowDefinition package through a structured interview. Use when authoring a new workflow from an idea, editing an existing workflow folder, or reviewing whether a workflow follows the golden standards. Interviews the user, challenges the design toward the standards, generates the package, and validates the .wd.json against the current checkout. Triggers include "design a workflow", "author a workflow", "create a .wd.json", "build a workflow package", "edit this workflow", "new Mediforce workflow".
Review pull requests, branches, or your own pre-PR diff along three parallel axes — Standards (file-by-file conventions, dead code, DRY/KISS, comments), Spec (does it match the originating issue/PRD), and Big Picture (scope creep, removable features, duplicated mechanisms). Use when asked to review a PR, diff, branch, specific files, or your own changes before shipping.
Write a Discord update for the MediForce community from rough notes. Use when the user asks for a "Discord update", "Discord post", "community update", "weekly digest for Discord", or hands over bullet-point notes to turn into a community announcement. Produces two versions (short and detailed) in engineer-to-peers tone, no marketing language.
Write and run L4 UI E2E journey tests. Use when implementing UI features (TDD red-green), adding tests for existing features, or when E2E tests need updating. Handles the workflow: write test → run → green.
Write a new test for a feature, endpoint, handler, or pure function. Use when adding test coverage for new or changed code, or when starting a feature TDD-style (RED → GREEN). Triggers include "write a test for", "add unit test", "add integration test", "add API E2E", "TDD this", "red-green this", "cover X with a test", "test plan for". Decides the right level (L1 unit / L2 integration / L3 API E2E / L4 UI E2E / L5 external), scaffolds the file, and walks the RED-GREEN loop. Use `/e2e-test` instead for the L4 UI journey workflow.
Keep project documentation in sync with code changes. Detects stale docs in current worktree diff (default), a specific commit, a PR, or across all monitored files (--audit). Auto-fixes Tier 1 executable docs (commands, ports, env vars); proposes Tier 2 narrative doc updates as an editable git diff. Triggers: "sync docs", "update docs", "check docs", "are docs up to date", "docs stale", "documentation outdated".
| name | renovate-review |
| description | Review and validate Renovate dependency PRs. Assesses risk, runs tests, fixes simple issues, and recommends merge/close/hold. Use when reviewing PRs from Renovate bot. |
| allowed-tools | Bash, Read, Glob, Grep, WebFetch |
| metadata | {"author":"Appsilon","version":"1.0","domain":"devops","complexity":"basic","tags":"renovate, dependencies, review, ci"} |
/renovate-review # review all open Renovate PRs
/renovate-review 77 # review a specific PR
List all open Renovate PRs and triage them:
gh pr list --author "renovate[bot]" --state open --json number,title,statusCheckRollup
Group PRs by ecosystem before processing:
| Ecosystem | Packages | Why group |
|---|---|---|
| React | react, react-dom, @types/react, next | Must be compatible; test together |
| Radix UI | @radix-ui/* | Shared versioning, test together |
| Firebase | firebase, firebase-tools, firebase-admin | Shared auth/SDK, test together |
| Testing | vitest, @playwright/test, @testing-library/* | Test infra, validate independently |
| Build | typescript, tailwindcss, postcss, autoprefixer | Build chain, may interact |
PRs in the same ecosystem should be checked out together (stack branches or merge locally) and tested as a group — if one breaks, the others may fix it or depend on it.
Process order: Low risk first (quick wins), then Medium, then High. For each PR (or ecosystem group), follow the single-PR workflow below.
Present a summary table at the end:
| PR | Package | Risk | Verdict |
|----|---------|------|---------|
| #77 | recharts 3.7→3.8 | Low | MERGE |
| #65 | typescript 5→6 | High | HOLD — breaking changes, see migration notes |
Given a Renovate PR number, review it end-to-end:
gh pr view {{NUMBER}} --json title,body,changedFiles,statusCheckRollup
Note the title (package + version), changed files, and CI status.
| Risk | Examples |
|---|---|
| Low | devDependencies, Docker tags, tooling (eslint, prettier), lockfile-only |
| Medium | CSS framework (tailwindcss), runtime utils (date-fns, clsx), test libs |
| High | Framework (next, react), core lib (zod, firebase), language (typescript) |
Major version bumps (e.g., 5→6, 18→19) are always at least Medium, even for low-risk packages. For High-risk major bumps:
gh api "repos/{owner}/{repo}/releases/latest" --jq '.body' 2>/dev/null
If all checks already passed on the PR branch, note it — this significantly reduces risk. If checks are still running, wait or note the pending status.
gh pr checkout {{NUMBER}}
pnpm install
Run validation in order (stop on first failure):
pnpm typecheckpnpm test:affected — if the change touches tested codepnpm test:unit — full unit suitepnpm test:e2e — only if the change touches UI framework, React, or Next.jsIf tests fail, assess whether the fix is simple (< 15 min of work):
Use exactly one of these verdicts:
Provide a one-sentence summary and wait for the merge/close decision. Format:
## Renovate: <package> <old> -> <new>
**Risk**: Low/Medium/High
**CI**: Passed / Failed / Pending
**Local validation**: typecheck OK, tests OK (N passed), e2e skipped
**Verdict**: MERGE / MERGE after fix / CLOSE / HOLD
<one sentence explaining why>
git checkout -pnpm install changes the lockfile beyond what Renovate committed, note it