'pull-request' 검색 결과

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.

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

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.

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

Creates pull requests with generated descriptions. Triggered when: PR creation, pull request, merge request, code review preparation.

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

Canonical rules for finding, creating, and updating Shift GitHub issues. Use whenever the user asks to file, create, open, update, triage, or search for an issue, or when substantial work needs an issue before a pull request. Prevents duplicates and defines acceptance criteria and pull-request closure semantics.

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

Prepares pull requests by running quality gates, drafting descriptions, and validating tests. Use when completing a feature and ready for review.

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

CodeRabbit reviews pull requests with AI on GitHub, GitLab, Azure DevOps and Bitbucket, and reviews local changes from a CLI before they are pushed. Use when a user asks to set up automated PR reviews, write or validate a .coderabbit.yaml, add path-specific review instructions, control a review with @coderabbitai commands, or run coderabbit review from the terminal or a coding agent.

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

Code review specialist for quality standards, design patterns, security review, and constructive feedbackUse when "code review, pull request, PR review, code quality, refactor, technical debt, design pattern, best practice, code-review, quality, patterns, security, refactoring, best-practices, pull-request, review, ml-memory" mentioned.

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

The art of reviewing code that improves both the codebase and the developer - sharing knowledge, maintaining standards, and building cultureUse when "code review, PR review, pull request, merge request, review comments, LGTM, review feedback, approve PR, request changes, review checklist, code quality, review standards, code-review, pull-request, PR, quality, standards, feedback, collaboration, mentoring" mentioned.

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

Closes a completed development branch by checking the final diff and proof, presenting merge, pull-request, keep, or discard options, and cleaning up only after the user or repository workflow chooses a path. Use when feature work is complete and the branch must be integrated or retired. Not for claiming a feature is complete before verification.

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

Bitbucket Pipelines migration to GitHub Actions — syntax mappings and the migration report template for Pipelines, Pipes, parallel steps, branch/pull-request workflows, deployments, variables. Load with `migration-core` when migrating Bitbucket Pipelines sources to GitHub Actions.

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

Guides pull request creation and review, including posting findings, controlling scope, readying work for review, and splitting work into a stacked-PR chain.

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

Start a local Git rebase when the user explicitly requests replay of a named source ref, or of the current branch, onto a named target, including a rebase-then-push request, which carries exact-lease publication to the branch's own remote destination, or continue or abort an active rebase. Use only when local history replay will start or is active; do not use for merge-based branch updates, repository merge settings, pull-request or merge-request merging, or push-only requests.

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

Use when you need pull-request review help

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

Take a change through a pull request in the pnpm repository — opening it, then staying with it after every push until CI is green and the review round is quiet. Use when opening a PR, after pushing to one, when a check fails, or when review comments arrive.

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

Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate, edit, apply, push, or merge the patch.

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

Contribute to OpenClaw ecosystem projects (OpenClaw, NemoClaw, NanoClaw) through a structured 9-step workflow: target verification, codebase exploration, parallel audit, finding cross-reference, and pull request creation. Emphasizes false positive prevention and project convention adherence.

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

Dispatch code-reviewer agent for two-stage review. Use after completing implementation tasks.

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

Complete development with structured merge/PR options. Use when ready to merge or submit work.

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

Use when asked to commit and push a feature branch, with or without a pull request. Its no-PR mode publishes without a PR. Not for a PR body alone: use create-pull-request.

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

Use when asked to create or update a PR, revise its description, or link issue references to its body. Not for multi-PR stacks: use gate-and-merge. Not for releases: use git-workflow-and-versioning.

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

Inspect one bounded Proto UI pull-request slice, produce canonical review input, and route each eligible exact head toward review and integration. Use for review queues, linked work, evidence gaps, merge conflicts, stale revisions, or portfolio health. This evidence leaf is read-only; authorized review and integration continue in their registered leaves.

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

Independently review a Proto UI change against current authority, bounded scope, executable evidence, projections, provenance, and integration conditions. Use for pull-request review, acceptance review, pre-merge audit, or fresh-context verification. Do not use to approve one's own work.

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

ALWAYS use this skill when creating pull requests. Applies Shipfox agent sequencing for GitHub CLI review preparation and pull-request creation. Trigger on create PR, open PR, submit PR, make PR, push and create PR, or prepare changes for review.

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

Prepare logical commits, publish through Pharos’s protected-main pull-request gate, monitor deployment, and hand off operational acceptance. Use only when commit, push, publish, release, or deployment watching is requested.

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