Skip to main content

kodus-pr-suggestions-resolver

Use when the user wants to fetch, triage, or implement Kodus suggestions for an existing remote pull request via `kodus pr suggestions`, `--pr-url`, or `--pr-number`.

설치로 이동

소스 정보

저장소
kodustech/kodus-ai
최근 소스 활동
2026년 4월 27일 12:44
감지된 SKILL.md 언어
영어
스타
1,389
포크
152

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
kodus-pr-suggestions-resolver
description
Use when the user wants to fetch, triage, or implement Kodus suggestions for an existing remote pull request via `kodus pr suggestions`, `--pr-url`, or `--pr-number`.
# Kodus PR Suggestions Resolver ## Overview Fetch PR suggestions via Kodus CLI, triage each suggestion against the PR goal, apply safe fixes, then validate with build/tests and report results. ## Workflow ### 1) Collect the PR target - If the user did not provide a target, ask for one of: - `--pr-url <url>` - `--pr-number <number>` with `--repo-id <id>` - If multiple are provided, prefer `--pr-url`. ### 2) Run Kodus suggestions Use: ``` kodus pr suggestions --pr-url <url> ``` Or when the URL is not available: ``` kodus pr suggestions --pr-number <number> --repo-id <id> ``` ### 3) Analyze suggestions with PR intent in mind - Extract or confirm the PR goal from the user or PR context. - For each suggestion: - Verify it does not conflict with the PR objective. - Prefer small, low-risk changes that improve the PR without changing scope. - Skip suggestions that are irrelevant, risky, or scope-expanding; note why. ### 4) Apply fixes one by one - Make changes per accepted suggestion. - Keep edits minimal and focused. - If a suggestion is unclear, ask a clarifying question before changing code. ### 5) Validate with build/tests (when available) - Run the most relevant build or tests for the edited area. - If no tests are available or running them is not possible, state that explicitly. ### 6) Report results Provide a concise report covering: - Suggestions applied (with brief rationale). - Suggestions skipped (with reasons). - Tests/builds run and outcomes. - Remaining uncertainties or follow-ups needed.
GitHub에서 보기