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

pr-post-push-sop

Use every time you push a commit to an active pull request, to verify the PR is truly stable before reporting merge readiness. Covers the post-push wait window, AI review audit (Copilot/Greptile/Codex), and the gh commands to snapshot PR state. Trigger on "I pushed" or "is the PR ready to merge".

インストール方法を見る

含まれるファイル(1)

  • SKILL.md1.9 KB

SKILL.md(原文)

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

PR Post Push SOP

Use this skill every time you push a commit to an active pull request. This is the Claude Code mirror of .opencode/skills/pr-post-push-sop/SKILL.md.

Objective

Make sure the PR is truly stable before reporting merge readiness.

Required Loop

  1. Capture current PR state and checks.
  2. Audit unresolved AI review feedback (Copilot, Greptile, Codex) across:
    • Review threads (paginate until hasNextPage=false)
    • PR issue comments for bot follow-ups
  3. Fix, reply, and resolve all actionable AI comments.
  4. Re-run relevant local checks for the latest changes.
  5. Push updates.
  6. Wait at least 5 minutes after the latest push.
  7. Re-run the review and checks audit.
  8. Only mark merge-ready if:
    • Required checks are green
    • No unresolved actionable AI feedback remains
    • No new AI comments arrived during the wait window

Command Hints

gh pr view <PR> --json url,headRefName,statusCheckRollup,mergeable,updatedAt
gh api graphql -f query='query($owner:String!, $name:String!, $number:Int!, $after:String){ repository(owner:$owner,name:$name){ pullRequest(number:$number){ reviewThreads(first:100, after:$after){ pageInfo{hasNextPage endCursor} nodes{ id isResolved isOutdated comments(first:50){ nodes{ id author{login} body createdAt } } } } } } }' -F owner=<OWNER> -F name=<REPO> -F number=<PR> -F after=<CURSOR_OR_null>
gh pr view <PR> --comments

Repo Rules Reminder

  • Prefix GitHub prose with [AGENT].
  • Never skip pagination for review threads.
  • Do not force push or amend unless explicitly requested.

レビュー

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

同じリポジトリのスキル

概要と使いどころ

Analyze Chronote product adoption with PostHog and Langfuse, including active users, meetings, feature usage, AI telemetry, and privacy-safe resolution of active Discord guild IDs to live server names.

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

Chronote-gg/Chronote42026年10月12日 更新

Use when a change affects user-visible behavior at docs.chronote.gg and needs public documentation. Covers where docs live (apps/docs-site vs docs/), authoring checklist, yarn docs:check, and Algolia config. Trigger when the user mentions docs, release notes, what's-new, or user-facing PR changes.

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

Chronote-gg/Chronote42026年10月12日 更新

Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation. Use when a user asks to investigate, root-cause, or plan changes, or when an Issue or PR is referenced and needs a plan.

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

Chronote-gg/Chronote42026年10月12日 更新

Query aggregate Langfuse cost, volume, latency, and model telemetry efficiently with Metrics API v2. Use for dashboards, rollout checks, usage summaries, and cost or latency comparisons; use Observations API v2 instead when individual rows are actually required.

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

Chronote-gg/Chronote42026年10月12日 更新

Configure and debug MCP servers for OpenCode, Codex CLI, and Claude Code, including auth headers, scope, and validation checks. Use when MCP tools fail to connect or when adding a new MCP server.

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

Chronote-gg/Chronote42026年10月12日 更新

Configure and debug MCP servers for Claude Code, OpenCode, and Codex CLI, including auth headers, scope, and validation checks. Use when MCP tools fail to connect, when an MCP server returns 401/404/HTML, or when adding a new MCP server to this repo.

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

Chronote-gg/Chronote42026年10月12日 更新

Chronote-gg のスキルをすべて見る

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