'prs' 검색 결과

Use when writing, testing, or preparing ANY contribution or pull request to the JSONbored/awesome-claude (HeyClaude) repo — adding a community content entry (agent/MCP server/skill/hook/command/rule/guide/collection/statusline), or making a platform/code change (website, registry package, MCP package, scripts). The repo has two separate review paths: a private, one-shot "HeyClaude submission gate" that decides single-file content PRs, and the shared gittensory-orb bot that posts an advisory readiness/linked-issue comment on platform/code PRs but does not itself merge or close content PRs. Unlike JSONbored/gittensory and JSONbored/metagraphed, a linked issue is OPTIONAL here — do not import their mandatory-linked-issue rule into this repo. Invoke for any "contribute to / open a PR against / submit an entry to / fix a bug in awesome-claude (HeyClaude)" task.

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

Separate a messy working tree with multiple tangled features into clean, focused PRs. Use when: (1) Working tree has uncommitted changes from multiple features mixed together, (2) Need to create a PR for just one feature from a mixed working tree, (3) "git stash pop" fails with "already exists, no checkout" for untracked files, (4) Pre-commit hooks block commits due to unrelated untracked files with errors, (5) Interface changes in one feature break consumer files from another feature in the same working tree. Covers git stash workflows, branch separation, conflict resolution, and pre-commit hook workarounds. Never stack PRs — always target main.

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

Unified GitHub triage for issues AND PRs. Classifies open items, answers questions from codebase, analyzes bugs, reviews PRs, and produces a structured triage report. Triggers: 'triage', 'triage issues', 'triage PRs', 'github triage'.

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

This skill should be used when a session's job is POST-MERGE VERIFICATION — taking merged PRs and establishing whether the change actually does what it claimed, then recording the result against its `pr_verifications` obligation. "validate the merged PRs", "work the verification backlog", "did that PR actually work", "run the post-merge E2E". It owns the obligation ledger the repo-pulse worker fills. Do NOT load it for building a change and opening its PR (that is `genesis-development`), or for driving open PRs to merge (that is `closing-session`).

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

Review other contributors' PRs to learn the codebase and build maintainer trust. Guides structured diff reading, helps formulate review comments, and teaches how to distinguish blocking issues from nits. Use when you want to learn a codebase by reviewing PRs, build trust with maintainers before contributing code, or practice code review on OSS repos. Not for reviewing your own PR — use oss-submit-pr for that.

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

Watch the PRs of one or more repos in this workspace — open a review session on an "/open-pr" comment, and a fix session on your own PRs' new findings when you say "Fix now" — then relay questions, drafts and results here. Use when asked to watch, auto-review or auto-fix a repo's PRs; optional `review`/`fix` and PR URLs.

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

Scan every open pull request in a GitHub repository, filter to the ones that are genuinely mergeable now, and report a compact verdict with a suggested merge order. Use when the user asks which PRs can be merged, wants an open-PR backlog triaged or reviewed in bulk, asks why a PR is blocked, or wants to clear a queue of stale or bot-reviewed PRs.

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

Use when acting as the orchestrator agent that drives Syntropic137 - running the dogfood loop, deciding what to dispatch next, landing agent PRs, deploying a beta, triaging failed executions, or keeping the scratchpad, paper cuts and retrospectives current. Trigger phrases include "orchestrator tick", "keep the loop running", "what should we dispatch next", "land these PRs", "why are PRs stacking up", "deploy the next beta", "pit stop", "the run failed, what now", "write the retro", "is the system helping", "scale quality", "learning loop for the orchestrator". Do NOT use for deciding whether one task belongs in a workspace or locally (see `dogfooding`), for turning one incident into an eval case (see `learning-loop`), for designing a workflow A/B experiment (see `workflow-experimentation`), or for release-branch and version-bump mechanics (see `devops`).

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

Monitor PRs, fix CI failures, address review comments, resolve merge conflicts, and restack stacks. Supports independent PRs, Graphite stacks, and GitHub stacked PRs (gh-stack).

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

Runs the daytime maintainer loop for NemoClaw, prioritizing items labeled with the current version target. Picks the highest-value item, executes the right workflow (merge gate, salvage, security sweep, test gaps, hotspot cooling, or sequencing), and reports progress. Use during the workday to land PRs and close issues. Designed for /loop (e.g. /loop 10m /nemoclaw-maintainer-day). Trigger keywords - maintainer day, work on PRs, land PRs, make progress, what's next, keep going, maintainer loop.

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

OpenClaw의 PR과 Issue가 기존 작업과 중복되는지 근거로 판단하고, prtags에서 관련 작업을 하나의 그룹으로 묶어 판단 이유와 확신도를 기록합니다.

• PR과 기존 작업의 중복 여부를 확인합니다
• 같은 문제를 보고한 Issue를 찾습니다
• 관련 작업을 하나의 중복 그룹으로 묶습니다

Repair confirmed failures in CI, the automated build and test process, starting with the base branch. Then prepare affected pull requests individually, recording checks for the exact code candidate and unresolved issues for owner review.

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

• Reproduce and repair CI failures on the base branch
• Investigate affected pull requests one at a time
• Verify required checks for the exact code candidate

Analyze all open GitHub issues and pull requests, then produce reports backed by links to specific code commits. Assess bugs, feature requests, and merge readiness without changing anything on GitHub.

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

• Reviewing a backlog of open issues and pull requests
• Checking whether reported bugs are already fixed
• Assessing pull request readiness for merging

Organize dependent changes into a chain of branches and pull requests so reviewers can inspect one layer at a time. Use the GitHub CLI extension to create, update, synchronize, and merge the chain.

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

• Splitting a large change into reviewable pull requests
• Updating a lower branch and rebasing dependent branches
• Synchronizing local branches with GitHub

Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.

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

• Draft notes for a stable or RC release
• Summarize changes since the previous published release
• Explain breaking changes with migration guidance

Build a tabbed project status page with goals, workstreams, owners, risks, and next actions. Publish it privately on claude.ai, then refresh the same URL from current sources and report what changed since the previous update.

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

• Sharing progress across multiple workstreams
• Tracking a software migration across several PRs
• Summarizing research or launch milestones

Review open pull requests against the actual release branch, inspect code changes and failed checks, and produce an evidence-based table recommending direct integration, selective reuse, deferral, or closure, with contributor credit.

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

• Reviewing the open pull request queue
• Selecting contributions for an upcoming release
• Checking conflicts against a local release branch

Integrate or upgrade cache-dit in SGLang diffusion, the image generation system. Follow guidance for resolving code conflicts, adding cache settings, testing feature combinations, and comparing generated images using quality measurements and logs.

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

• Upgrading cache-dit in SGLang diffusion
• Resolving conflicts when porting upstream changes
• Adding per-request cache settings

Coordinate multiple agents to maintain context-mode, from sorting GitHub issues and reviewing pull requests to preparing releases and announcements. Workflows require reproduced bugs, source evidence, test-first changes, and checks across supported platforms.

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

• Investigating reported bugs and their history
• Reviewing contributor pull requests
• Preparing releases and compatibility checks

Merge GitHub pull requests while preserving credit for the original contributors. Covers straightforward merges, conflict resolution, selective file inclusion, duplicate PR closure, and checks that confirm both attribution and working code after integration.

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

• Merge external contributions while preserving author credit
• Resolve conflicts in a pull request
• Merge selected files from a pull request

Set up recurring agent work for issues, tickets, or small fixes. The skill tests one real item first, then defines a repeatable procedure, tracks work to prevent duplicates, and holds outputs for human review.

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

• Recurring preparation of fixes for Sentry issues
• Drafting replies to Front tickets
• Preparing small performance improvement PRs

Review open GitHub issues and pull requests against project templates and contribution guidelines. Get a report on missing information and compliance, with options to apply recommended labels or close incomplete submissions with an explanatory comment.

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

• Reviewing open issues in bulk
• Checking pull requests against templates
• Applying labels based on review results

Work through unresolved review comments across dependent PRs managed with Graphite. Review branches from the base upward, propose fixes or replies for approval, test changes, and commit each branch locally while preserving stack dependencies.

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

• Review unresolved comments across a Graphite stack
• Fix review findings with regression tests
• Explain findings already addressed in a later PR

Navigate Apache Beam contributions from finding an issue to submitting a pull request, a proposed code change, and responding to reviews. Covers environment setup, tests, formatting, licensing requirements, and closer evaluation of changes to core components.

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

• Prepare a first Apache Beam contribution
• Organize a pull request and its related issue
• Check tests and formatting before submission