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,409
分支
153

安装方式

默认使用会先检查来源的 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 查看