'prs' 검색 결과

Audit changed code by tracing execution paths and matching them to existing tests. Show coverage gaps and test quality, then generate tests for high-priority gaps using the project's current framework, helpers, and naming conventions.

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

• Find missing tests before shipping a PR
• Check coverage of error handling and guard clauses
• Generate tests using existing project conventions

Check specific documentation pages against source code, one factual claim at a time. Receive verdicts showing supported, partly supported, contradicted, or unsupported statements, with code file and line references and suggested corrections.

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

• Fact-check a specific documentation page
• Find inaccurate claims within a paragraph
• Verify documentation changes against implementation

Build an implementation queue from accepted GitHub issues and distribute them to dedicated workers. Record selection reasons, check for existing pull requests, and process the full queue with a configurable concurrency limit, defaulting to two workers.

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

• Queue accepted issues for implementation
• Limit concurrent issue delivery workers
• Record why issues were included or skipped

Organize pull request reviews by selecting eligible labeled or explicitly named requests and distributing them to a dedicated worker pool. It records selection decisions and limits concurrent reviews, with two worker sessions by default.

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

• Reviewing a selected list of pull requests
• Processing a labeled review queue with limited concurrency
• Checking code owner conditions before scheduling reviews

Organize complex feature work into exploratory prototypes, written behavior contracts, shared tests, and focused pull requests. Use this workflow to settle interfaces before review, split large changes around clear responsibilities, and handle review findings without expanding scope.

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

• Planning a feature that changes multiple public interfaces
• Resolving interface changes that recur during review
• Splitting a large branch into focused pull requests

Checks whether work is truly complete before reporting success, committing changes, or creating a pull request. It runs the relevant checks, reads their full output, and ties status reports to current evidence.

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

• Checking results before reporting completion
• Confirming that a bug fix resolves the original problem
• Verifying work before a commit or pull request

Organize mixed Git changes into focused commits and pull requests that reviewers can follow. It preserves unrelated work, checks proposed changes for private information, runs relevant validation, and pushes or opens pull requests when authorized.

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

• Splitting mixed changes into focused commits
• Checking changes for private information before publication
• Preparing pull requests with validation results

Use the gh command-line tool to work with GitHub issues, pull requests, and automated checks. Inspect failed workflow steps and logs, retrieve additional data through the API, and extract selected fields from structured results.

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

• Check automated test status on a pull request
• Inspect logs from failed workflow steps
• List issue numbers and titles

Use the gh command-line tool to manage GitHub issues and pull requests, check CI automated checks, and inspect workflow failures. Retrieve failed-step logs or query the GitHub API for specific information in structured output.

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

• Creating pull requests
• Listing repository issues
• Investigating failed CI checks and logs

Review a Marin pull request as a complete change, checking how it fits existing code, where simpler structures could work, and what might break beyond the edited lines. Receive findings with evidence and concrete replacements.

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

• Reviewing the design of a large pull request
• Checking structural issues in AI-generated code
• Investigating effects beyond the edited lines

Preview pending infrastructure changes in a specified Marin Pulumi stack without applying them. Trace each change to supporting code and merged pull requests when deployment history provides a reliable Git baseline.

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

• Checking pending infrastructure changes before deployment
• Finding pull requests that explain resource changes
• Investigating differences without a matching code change

Prioritize open LinkedIn integration issues and pull requests, or proposed code changes, using report completeness, severity, reach, and readiness checks. Produce ranked lists, identify missing evidence, and recommend concrete next steps for maintainers.

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

• Prioritizing a backlog of open issues
• Separating reports that need more evidence
• Comparing pull requests for production readiness

Search GitHub code, repositories, issues, and pull requests through MCP, a connection to external tools. Use GitHub search syntax and owner or repository filters to find implementation examples, bug reports, and project information.

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

• Find implementation examples across repositories
• Find critical bug reports
• Find related pull requests

Search Wayback Machine archives for deleted GitHub files, issues, pull requests, and wiki pages. Recover available text and repository details from saved web pages to investigate a project's past state.

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

• Recovering a deleted README or documentation
• Checking deleted issue and pull request discussions
• Reviewing a repository's past state

Investigate GitHub security incidents by querying archived public activity with BigQuery. Recover recorded details of deleted issues and pull requests, identify the accounts involved, and reconstruct timelines to check claims about repository activity.

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

• Reconstructing a security incident timeline
• Recovering recorded text from deleted issues or pull requests
• Checking claims about repository activity

Split a pull request into smaller drafts based on CODEOWNERS, the file that assigns review ownership. Propose groups of changes that need fewer reviewer teams, keep tests with their code, and create the drafts after approval.

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

• Split a large pull request into smaller reviews
• Reduce reviewer groups required for each pull request
• Plan dependencies between split pull requests

Modify NVIDIA cuOpt itself, covering C++/CUDA solver code, Python bindings, server endpoints, and CI. Follow project conventions for environment setup, builds, tests, debugging, and contributions, including the required sign-off for submitted changes.

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

• Fixing solver internals and investigating numerical issues
• Changing Python APIs or server endpoints
• Setting up a development environment and running tests

Triage and review all open GitHub issues and PRs against project templates and contribution guidelines

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

Autonomous PR merge pipeline. Scans all repos for open PRs, dispatches subagents to fix CI, resolve conflicts, address review comments, then merges. Use --main to also sync dev↔main branches.

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

Autonomous multi-project orchestration engine. Audits all registered projects, structures work into dependency-wired tasks, dispatches parallel agents (subagents or Agent Teams), audits completions, and ships PRs. Registry-driven — works for any user with a configured project registry.

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

Business-level "what should I do next". Priority stack — fires > unread comms > ready-to-merge PRs > Linear sprint > revenue-generating GSD work. Uses pre-gathered data and routes to the right skill.

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

Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio). Manage code workflows, review PRs, search code, and handle deployments programmatically.

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

Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `samber/cc-skills-golang@golang-project-layout` (splits), `samber/cc-skills-golang@golang-modernize` (idioms), `samber/cc-skills-golang@golang-code-style` (control flow), `samber/cc-skills-golang@golang-design-patterns` (patterns/DI).

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

Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by area.

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