Agent Skills › esengine/DeepSeek-Reasonix › issue-fix

issue-fix

GitHub

复现仓库问题，基于观察证据制定最小正确修复方案，添加回归测试并运行检查，最终起草符合规范的拉取请求。

examples/issue-fix-kit/skills/issue-fix/SKILL.md esengine/DeepSeek-Reasonix

Trigger Scenarios

用户报告代码缺陷或异常行为需要针对特定Issue进行修复和提交PR

Install

npx skills add esengine/DeepSeek-Reasonix --skill issue-fix -g -y

More Options

Non-standard path

npx skills add https://github.com/esengine/DeepSeek-Reasonix/tree/studio/examples/issue-fix-kit/skills/issue-fix -g -y

Use without installing

npx skills use esengine/DeepSeek-Reasonix@issue-fix

指定 Agent (Claude Code)

npx skills add esengine/DeepSeek-Reasonix --skill issue-fix -a claude-code -g -y

安装 repo 全部 skill

npx skills add esengine/DeepSeek-Reasonix --all -g -y

预览 repo 内 skill

npx skills add esengine/DeepSeek-Reasonix --list

SKILL.md

Frontmatter

{
    "name": "issue-fix",
    "owner": "@esengine",
    "backup": "@SivanCola",
    "status": "active",
    "reviewed": 1790812800,
    "description": "Reproduce a repository issue, make the smallest correct fix, and draft a pull request from observed evidence."
}

Issue fix

Use the repository selected for this session. Read its standing instructions and inspect its working tree before editing. Preserve existing changes.
Read the complete references/delivery.md beside this skill. Identify the issue's trigger, expected behavior, affected code, and acceptance checks. Resolve missing behavior before changing code; an issue title is not a spec.
Reproduce the trigger or trace its execution path. Record the command and observed failure. If reproduction is unavailable, state the limitation and the code or logs that support the proposed root cause.
Make a focused fix using the repository's existing patterns. Add or update a regression test for the trigger when feasible. Keep unrelated changes out of the patch and follow the repository's approval rules for wider changes.
Run the relevant checks and required repository gates. Report pass, fail, and not-run results separately. Review the final diff against the issue.
Draft the handoff using the reference format. Commit, publish a PR, or send a message only when the user has authorized that action.

The bundled references/scenario.md defines an optional local exercise. Use it only when the user selects that fixture; it is not the issue to apply to an arbitrary repository.