メニュー
Review a pull request for flying-dice/dcs-dropzone. Trigger on any request to 'review PR', 'review pull request', 'check PR', or 'look at PR'.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | review-pr |
| description | Review a pull request for flying-dice/dcs-dropzone. Trigger on any request to 'review PR', 'review pull request', 'check PR', or 'look at PR'. |
Always run git pull first to ensure local state is up to date.
gh pr view <NUMBER> --repo flying-dice/dcs-dropzone --json title,body,author,baseRefName,headRefName,additions,deletions,changedFiles,state,labels,reviews,comments
gh pr diff <NUMBER> --repo flying-dice/dcs-dropzone
gh pr checks <NUMBER> --repo flying-dice/dcs-dropzone
This repo has two required CI checks. Both must show pass before the PR can be considered green:
| Check | System | URL pattern |
|---|---|---|
build-app | GitHub Actions | github.com/flying-dice/dcs-dropzone/actions/runs/... |
dcs-dropzone | Jenkins | falcon.beluga-sirius.ts.net/job/dcs-dropzone/... |
If either shows pending, note it explicitly — do not declare CI green until both pass.
To dig into Jenkins results use mcp__jenkins__getTestResults and mcp__jenkins__getBuildLog.
To dig into GitHub Actions use gh run view <RUN_ID> --repo flying-dice/dcs-dropzone.
Structure feedback as:
git pull before reviewing.Write and debug Playwright E2E tests following project ADR TEST-006 conventions.
Write documentation for DCS Dropzone — a DCS World mod manager consisting of three apps: the Daemon (download, unpack, symlink management), the Webapp (hosted mod discovery), and the Launcher (auto-update). Use this skill whenever the user asks to create, write, review, or structure documentation for this project, including API reference pages, developer guides, landing pages, and — critically — Spec pages for Spec Driven Development (SDD). Spec pages are the primary artefact of SDD: they describe a single system behavior in terms of inputs and resulting system actions, completely void of technical implementation details, and serve as both documentation and the basis for test cases. Trigger on any request to 'write a spec', 'document this behavior', 'write docs', 'create a reference page', 'write a guide', or 'add a landing page' for any part of the project.
Pick an open GitHub issue from flying-dice/dcs-dropzone, implement it on a feature branch, raise a PR, and post progress updates to #dcs-dropzone on Slack using @here. Trigger on any request to 'pick an issue', 'work on an issue', 'grab an issue', 'pick up a ticket', or 'start an issue'.
Monitor GitHub Actions and Jenkins pipelines for the current branch/commit and confirm both are green before closing a work item. Trigger on any request to 'check pipelines', 'verify CI', 'watch the build', 'is CI green', 'check before closing', or 'monitor pipelines'.