'pull-request' 검색 결과

Drive a GitHub Copilot (or any bot reviewer) pull-request review to a clean pass without babysitting it: fix each finding in its own commit, reply to the review thread with the fix sha, resolve the thread, re-request the bot, and poll for the async re-review. Covers the thread node-id (PRRT_...) vs comment databaseId distinction, the resolveReviewThread GraphQL mutation, the copilot-pull-request-reviewer[bot] slug, and how to read the bot's verdict (COMMENTED plus a "human review recommended" banner is not a blocking finding). Use when Copilot has left review comments on your PR, when bot review threads must be closed out with an auditable fix-reply-resolve trail before merge, or when you need to verify that a re-review actually landed on the new HEAD rather than the old one.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review a pull request end-to-end using GitHub CLI. Covers diff analysis, commit history review, CI/CD check verification, severity-leveled feedback (blocking/suggestion/nit/praise), and gh pr review submission. Use when a pull request is assigned for review, performing a self-review before requesting others' input, conducting a second review after feedback is addressed, or auditing a merged PR for post-merge quality assessment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create and manage pull requests using GitHub CLI. Covers branch preparation, writing PR titles and descriptions, creating PRs, handling review feedback, and merge/cleanup workflows. Use when proposing changes from a feature or fix branch for review, merging completed work into the main branch, requesting code review from collaborators, or documenting the purpose and scope of a set of changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GitHub Issue群からClaude Code並列開発用の実行プロンプト集（docs/prompts/xxx.md）を自動生成するスキル。 「開発計画を作成して」「実行プロンプトを生成して」「dev-planを作って」「プロンプト集を作って」 「並列開発の計画を立てて」などのリクエストで発動。 Issue番号リストを受け取り、依存関係のWave構造を対話で決定し、 /gtr-workflow → 実装 → /e2e-test → /pull-request の一連の指示を各Issueごとに生成する。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Diagnoses CI and pull-request pipeline health for a GitHub repo using the engineering analytics MCP tools — pull-requests (PR list with CI status), workflow-health (per-workflow CI trends), and pr-lifecycle (a single PR's timeline). Use when asked whether CI is getting faster or slower, which GitHub Actions workflow is the slow or flaky long-pole, how long PRs take from open to merge, how an author's merge time compares to the cohort, which open PRs have failing or pending CI, or where a specific pull request is stuck. Triggers on "engineering analytics", "is CI getting slower", "slow workflow", "flaky CI", "time to merge", "cycle time", "PR throughput", "failing checks", "where is PR <n> stuck", "CI long pole", "what's holding up this PR".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Prepare completed changes for a GitHub pull request with organized commits, a clear title and description, verification evidence, screenshots for interface changes, and explicit replies to review comments through merge readiness.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing completed changes for a GitHub pull request
• Documenting verification and interface changes
• Replying to review comments and submitting fixes

Create a GitHub pull request that follows the project's template. Review commits and changed files, gather issue and testing details, check branch readiness, and use the GitHub CLI to submit a regular or draft request.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Submitting completed changes for review
• Writing a PR description from commits
• Creating a draft pull request

Guide a Verdaccio change through a pull request, from branch preparation and checks to changelog entries, labels, CI results, and review responses. Track separate pull requests when the fix also belongs on other release lines.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing and opening a pull request
• Investigating failed CI checks after a push
• Addressing review comments and updating the PR

Assess a fixed patch or pull request diff before merging. Trace affected behavior, evaluate regression risks, tests, and recovery options, then provide an evidence-based recommendation and advisory automatic-merge eligibility without modifying or merging the patch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess a generated patch before merging
• Trace how a pull request affects production behavior
• Evaluate tests and rollback options

Refresh evidence behind paid advertising guidance by checking platform changes, APIs, policies, regulations, and benchmarks. Record sources and contradictions, flag outdated or unsupported claims, and propose updates grounded in current primary sources.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Refreshing overdue advertising research
• Rechecking platform and API claims
• Reviewing evidence behind advertising benchmarks

Assess a fixed code patch for behavior changes, regression risks, test coverage, and recovery options. Receive an evidence-based report and structured assessment indicating whether it is ready to merge and qualifies as an automatic merge candidate.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing the risks of an AI-generated patch
• Checking affected behavior before merging a pull request
• Assessing whether tests protect changed behavior

Organize unresolved feedback on GitHub pull requests, group changes by file or behavior, and apply selected fixes locally. Run relevant tests and summarize completed work and remaining issues, with replies and thread resolution requiring explicit user direction.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Organizing unresolved pull request feedback
• Applying selected review fixes locally
• Testing changes and summarizing remaining issues

Publish validated gh-aw changes as a draft pull request from a cloud agent.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drive ONE already selected open pull request in microsoft/apm to mergeable. Classifies copilot-pull-request-reviewer[bot] inline review, runs autopilot-pr-review-worker, folds (by default) every recommendation inside the PR's stated scope, pushes to the head branch or a superseding PR that preserves authorship via commit trailers, watches CI to green (`agent-merge` when that skill or `<agent_merge_state>` is present; otherwise `gh pr checks --watch`), and iterates under fixed caps until ready-to-merge, advisory-with-deferred, superseded, or blocked. Plan before any fold, push, or reviewer request. Never spawned by autopilot-pr-review-scheduler. That scheduler is advisory only. Invoke this skill by name when the caller asked to drive a PR to merge.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Apply Marin house style when producing or revising commit, pull-request, issue, comment, documentation, report, or blog prose.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Audit openai-go during scheduled or repeated maintainer runs for correctness bugs, security weaknesses, performance problems, rough edges, non-idiomatic Go, test gaps, code organization, and architecture, then report one prioritized recommendation with evidence. Use for recurring proactive repository maintenance and rotating whole-codebase review; do not use for feature work, code changes, autonomous publishing, or pull-request stewardship.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[omh] Commit message or pull-request body to write for a change: draft it in the repository's own convention, with `Tested:` listing only commands observed to run and everything prepared but not run under `Not-tested:`. Use when the user says: commit-pr-authoring, commit message, commit messages, write the commit message, draft the commit message, commit body, squash message, pr body.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a bounded CI contract gate for an Attio integration using fixtures, schema checks, and an optional read-only smoke request. Use when Attio changes need pull-request evidence without mutating CRM data. Trigger with "Attio CI", "test Attio integration", or "Attio pull request gate".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build and review a bounded CI gate for Algolia index configuration and disposable-index smoke tests. Use when search changes need pull-request evidence without mutating production. Trigger with "Algolia CI", "test Algolia in GitHub Actions", or "search deployment gate".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drafts or opens a GitHub pull request, runs changed-area preflight checks, and commits validated preflight repairs, and routes Azure DevOps repositories to the backlog-management pull request protocol. Use when a user asks to prepare, create, or update a pull request on GitHub or Azure DevOps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Code review automation for TypeScript, JavaScript, Python, Go, Swift, and Kotlin. Analyzes PRs for complexity, risk, SOLID violations, and code smells. Use when reviewing PRs, analyzing code quality, or generating review checklists.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Opens a pull request, publishing the current branch as a PR. TRIGGER when: the user wants to open a pull request, publish the current branch as a PR, or take the current work through to an open PR. DO NOT TRIGGER when: only committing changes → commit; babysitting CI after the PR is already open → monitoring-pull-requests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Rebases a feature branch onto its latest base, resolving conflicts while preserving the intent of local changes, optionally force-pushing and watching CI afterward. TRIGGER when: the user wants to rebase a feature branch, update a branch against its base, or replay local work on top of the latest upstream. DO NOT TRIGGER when: merging a release branch into dev → merging-branches; only watching CI on an already-open PR → monitoring-pull-requests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Watches an open pull request's CI until green and fixes failing checks. TRIGGER when: the user wants to watch a pull request's CI, babysit a PR until it goes green, or fix failing CI checks on an open PR. DO NOT TRIGGER when: opening the PR in the first place → pr; rebasing the branch onto its base → rebase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.