스킬 찾기

Audit existing SKILL.md files for clear activation conditions, usable instructions, and defined outputs. Get prioritized findings and specific improvements, with changes applied only when requested and the author's intent preserved.

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

• Audit existing skills for quality issues
• Clarify when a skill should activate
• Move lengthy examples into supporting files

Group bug reports by their underlying cause and plan shared fixes. This skill guides reproduction, checks for unnecessary complexity, and requires named test evidence before treating related issues as resolved.

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

• Grouping accumulated bug reports by root cause
• Planning one fix for several related issues
• Checking test evidence before closing issues

Prepare Gentle AI changes for review by linking approved issues, following branch and commit naming rules, and drafting pull requests with observed test results. Check change size and required automated checks before claiming readiness.

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

• Preparing a branch for a fix or feature
• Drafting a pull request linked to an approved issue
• Organizing test results and reviewer notes

Guide changes to RDD reviewer integrations through a shared Go contract, a common set of processing rules. Define adapter boundaries, validate result handling, and check that runtime migrations preserve existing review outcomes.

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

• Moving reviewer invocation into a shared Go contract
• Checking that adapters only invoke reviewers and return raw output
• Verifying review outcomes during a runtime migration

Plan commits around complete features, fixes, or documentation changes, keeping related tests and docs together. Split larger work into reviewable units with recorded verification results and clear boundaries for rolling back changes.

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

• Split a feature into reviewable commits
• Keep tests and documentation with related code
• Plan related pull requests for a large change

Split changes exceeding 400 lines into linked pull requests with clear boundaries and dependencies. Choose a chain structure, keep tests and documentation with each work unit, and document review order, verification plans, and justified size exceptions.

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

• Splitting a change that exceeds 400 lines
• Planning PRs that can merge independently
• Coordinating a feature through a draft tracker PR

Write and review Go tests using patterns suited to functions, file operations, and terminal interfaces. Cover multiple scenarios, check state changes, and compare rendered output with saved expected results while keeping slow integration tests separately skippable.

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

• Testing Go functions and parsers across multiple cases
• Checking file operations in temporary directories
• Testing Bubbletea state changes and interactions

Coordinate temporary agents for code exploration, independent implementation tasks, verification, reviews, or complex debugging. Define self-contained assignments, run independent work in parallel, and check returned evidence before combining the results.

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

• Delegating codebase exploration to inform a decision
• Running independent implementation tasks in parallel
• Getting an independent check of a high-risk change

Run two independent reviewers against the same fixed target, then compare their findings. With approval, address severe issues confirmed by both and reassess the fixes, using at most two correction rounds before a final verdict.

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

• Request two independent reviews of a specific target
• Separate confirmed issues from disputed findings
• Fix severe issues confirmed by both reviewers

Audit groups of bug reports to find shared root causes, checking claims against current code and tests. Produce a cause map, prioritize fixes that remove faulty mechanisms, and document which issues have enough evidence to close.

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

• Grouping backlog issues by shared root cause
• Checking whether old bug reports still apply
• Comparing fixes that remove faulty mechanisms

Structure guides, READMEs, design documents, and pull request descriptions so readers can find answers quickly. Put outcomes first, introduce details gradually, and use examples, tables, and checklists to support understanding and review.

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

• Reorganizing a long or dense README
• Writing an onboarding guide for new contributors
• Making a pull request's review steps clear

Prepare and manage GitHub bug reports and feature requests using repository evidence and required forms. Check for duplicates, identify missing information, and verify published issues or comments before reporting the result.

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

• Preparing a bug report using the required issue form
• Checking for duplicate feature requests
• Adding information to an existing issue

Build and refresh an index of available skills, including when to use each one and its exact file path. Resolve duplicate entries and give agents a current reference after skills are added, removed, moved, or renamed.

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

• Refreshing the index after adding or removing skills
• Resolving duplicate user and project skills
• Finding exact skill paths before delegating work

Create and verify gentle-ai journeys, which are scripted sequences of product actions. Check their declarations separately from actual execution, review outdated expectations after behavior changes, and record execution results for pull requests.

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

• Adding a product operation journey
• Updating expectations after behavior changes
• Reproducing a bench failure from CI

Prepare external contributions to gentle-ai through approved issues, accurate pull request descriptions, and plans for splitting large changes. Check claims against test results and GitHub state while respecting contributor and maintainer permissions.

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

• Prepare a contribution through the approved issue workflow
• Audit pull request claims against GitHub state
• Plan a sequence of related pull requests

Prepare pull requests by checking approved issue links, change-type labels, and required automated checks. Draft the repository’s PR template using observed test results, while leaving commits, pushes, PR creation, and merging under human control.

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

• Preparing a branch for review
• Drafting a PR linked to an approved issue
• Checking required CI before declaring a PR merge-ready

Turn reusable workflows and project conventions into concise instructions for AI agents. Structure SKILL.md with required metadata, move supporting material into local files, and register project skills in AGENTS.md when applicable.

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

• Turning a recurring workflow into an agent skill
• Documenting project conventions for AI agents
• Moving lengthy explanations into supporting files

Draft clear, considerate comments for code reviews, issue replies, and team updates. Put the actionable point first, explain technical reasons when needed, and give a concrete next step while matching the conversation’s language.

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

• Requesting a code change with a clear reason
• Replying to a contributor’s issue
• Writing a brief asynchronous team update

Split large code changes into linked pull requests, each with a focused scope. Organize their order, dependencies, and verification steps so reviewers can assess one unit of work at a time.

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

• Splitting a pull request with more than 400 changed lines
• Planning the review order for dependent changes
• Integrating a feature through a shared branch

Guide an approved defect fix from reproduction on current main through testing and independent validation. Record evidence for each operator workflow, track change size and rollback scope, and apply review records when receipt-driven development is enabled.

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

• Reproducing approved defects before implementation
• Recording runtime evidence for CLI and lifecycle flows
• Splitting fixes by cause and rollback scope

Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.

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

Design docs that reduce cognitive load. Trigger: writing guides, READMEs, RFCs, onboarding, architecture, or review-facing docs.

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

Trigger: PRs over 400 lines, stacked PRs, review slices. Split oversized changes into chained PRs that protect review focus.

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

Trigger: judgment day, judgement day, dual review, adversarial review, juzgar. Run explicit blind dual review with at most two scoped fix/re-judgment rounds.

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