本文へ移動
cccskills
無料GitHub で公開

reviewing-pull-requests

Reviews a pull request in a separate subagent that has not seen this conversation, applying the rules in REVIEW.md. TRIGGER when: this session has just opened a pull request, for example with `gh pr create`; the user asks for a review of a pull request by URL or number; or a hook reports that large changes were pushed to a pull request. DO NOT TRIGGER when: answering existing review comments → addressing-review; watching CI → monitoring-pull-requests.

日本語の概要は準備中です。原文の説明を表示しています。

opsmill/infrahubスター 540(GitHub 540 + cccskills 0)
連携ツールGitHub

実行スコア 未検証

インストール方法を見る

含まれるファイル（2）

  • SKILL.md1.9 KB
  • agents/openai.yaml284 B

SKILL.md（原文）

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Review a pull request with the code review built into the tool you are running in, without the conversation that wrote the change. The pull request is $ARGUMENTS; in Codex, take it from the request that started this skill, or use the pull request of the current branch.

  1. Read REVIEW.md at the root of the repository. Its rules decide what to report and how to rate it.
  2. Run the built-in review:
    • Claude Code: run the code-review skill with the arguments xhigh <pull request>.
    • Codex: find the base branch with gh pr view <pull request> --json baseRefName, or use the branch origin/HEAD points to when gh cannot reach GitHub. Start a new subagent that does not get this conversation, give it the task "Review the changes this branch would merge into origin/<base branch>, following Codex's built-in review instructions in ${CODEX_HOME:-$HOME/.codex}/skills/.system/review-agent/SKILL.md.", and wait for its result. Codex does not offer that skill by name, so the subagent reads the file. The pull request's branch must be checked out, as it is when this session opened the pull request.
  3. Return the findings with the rules in REVIEW.md applied, separating the issues this pull request introduces from older ones. Change no files.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

analyzing-ci-flakiness

無料

Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal ledger so flakiness can be tracked over time. TRIGGER when: the user wants to find flaky tests, correlate recent CI failures, check which tests fail across PRs or recover on retry, or refresh the flakiness trend report. DO NOT TRIGGER when: babysitting a single PR's CI until green → monitoring-pull-requests; diagnosing or fixing one specific failing test → the bug-analysis skills.

日本語の概要は準備中です。原文の説明を表示しています。

opsmill/infrahub5402026年10月29日 更新

audit-docs

無料

Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers, reports gaps, and optionally applies the fixes. TRIGGER when: the user wants to audit or check documentation coverage, find doc gaps after a feature branch, or verify docs are still current for a subject or specific files. DO NOT TRIGGER when: authoring new documentation from scratch → the writing-infrahub-docs skill from the OpsMill skills plugin; only linting/formatting Markdown → run `uv run invoke docs.lint`.

日本語の概要は準備中です。原文の説明を表示しています。

opsmill/infrahub5402026年10月29日 更新

commit

無料

Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream. TRIGGER when: the user wants to commit, save, or check in the current changes. DO NOT TRIGGER when: opening a pull request → pr.

日本語の概要は準備中です。原文の説明を表示しています。

opsmill/infrahub5402026年10月29日 更新

creating-changelog-entries

無料

Use when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or opening a PR, or whenever asked to add a changelog entry, towncrier fragment, or news fragment.

日本語の概要は準備中です。原文の説明を表示しています。

opsmill/infrahub5402026年10月29日 更新

creating-issues

無料

Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue. TRIGGER when: the user wants to file/open/create an issue, turn a feature idea or improvement into a ticket, or capture something missing or broken as a ticket. DO NOT TRIGGER when: breaking work into multiple issues or planning a body of work → a planning skill; writing a full Product Requirements Document → creating-prd; the idea is still fuzzy and unhardened → grilling-ideas first.

日本語の概要は準備中です。原文の説明を表示しています。

opsmill/infrahub5402026年10月29日 更新

creating-prd

無料

Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.

日本語の概要は準備中です。原文の説明を表示しています。

opsmill/infrahub5402026年10月29日 更新

opsmill のスキルをすべて見る

このスキルの問題を報告する