Treat issues found in review, testing, or runtime as traceable tickets. The input is one or more findings; the output is an item-by-item handling record, fixes verified by regression, and clear reasons and follow-up paths for items that cannot be fixed.
Scope of application
Applies to structured findings, failing tests, or locatable defects in ordinary engineering repositories. If the task is constrained by an organization's dedicated status, approval, or archival rules, load the corresponding binding layer first; this skill does not assume any specific directory, project, or toolchain.
Even a single obvious small change should retain a minimal record: reproduction evidence, fix, relevant regression, and receipt.
Customer-readable description
What this skill can do
| Customer wants | Execute closed loop | Customer can see |
|---|---|---|
| Fix review comments one by one | Summarize, decide, fix, and verify item by item | Status and evidence for each finding |
| Confirm whether it can be closed | Independently re-check fixes and regression results | Conclusion of pass, needs changes, or blocked |
| Defer some issues | Give a traceable follow-up location and reason | Clear deferral boundary |
How customers use it
Provide findings, the target workspace, relevant tests or reproduction information, and the allowed scope of changes. If something may involve deletion, overwriting, remote state, release, or scope expansion, obtain explicit authorization first; if information is insufficient, first organize the input list and do not start modifying.
Dependencies and installation
Installation:
npx skills add soia-team/soia-open-dev-coding-skills -g -a '*' -s soia-dev-fix-loop -y
This skill requires no other dedicated installation or private configuration. Its hard dependencies are accessible findings, the target workspace, and verification entry points commensurate with the risk; follow the target repository's existing contribution instructions and check conventions.
Logs and completion receipt
The process records the number of inputs, item-by-item decisions, verification status, and blocking reasons. The final receipt must cover the conclusion for each finding, the checks actually run, unhandled items, and residual risks; credentials or local private information must not be output.
Five-step fix loop
1. Reproduce and normalize input
Read all findings and extract unique identifiers, severity, location, problem description, and source. Merge duplicates; when the same issue has different severities, use the higher level while retaining the sources. Run a minimal reproduction for each key issue, or record why it cannot currently be reproduced.
| Finding | 严重性 | 来源 | 位置 | 复现证据 |
|---|---|---|---|---|
| F-01 | high | review-a | <file:line> | <命令或步骤> |
2. Decide item by item before fixing
Each finding must have a status selected before implementation:
| Decision | Meaning | Required basis |
|---|---|---|
| fix | Fix in this round | Target behavior and verification plan |
| reject | Finding does not hold | Testable rebuttal evidence |
| defer | Do not fix for now | Traceable follow-up location, owner, or trigger condition |
Do not silently omit issues; do not replace defer with "look at it later." For high-risk decisions or fixes that expand scope, first explain the impact to the user and obtain the necessary authorization.
3. Implement the minimal fix
Only modify the parts needed for the finding to satisfy the target behavior. Do not fake fixes with TODOs, comments, disabling exceptions, weakening assertions, or deleting tests. Each fix should have corresponding evidence in the diff; if multiple fixes depend on each other, explicitly state the dependencies.
After modification, search for similar patterns and decide whether to include them in this round; if excluded, record the scope rationale to avoid mistakenly calling unchecked similar issues resolved.
4. Regression and independent review
Each fix item must run at least one direct verification and run regression checks proportionate to the change surface. For each reject item, review its rebuttal evidence; for each defer item, review that the follow-up chain truly exists and is sufficiently specific.
In addition to tests, attack the conclusion using independent paths, such as checking the diff, constructing counterexample inputs, verifying callers, or having someone not involved in the implementation review it. If regressions, an empty diff, TODO fake fixes, invalid rejection reasons, or broken follow-up chains occur, loop back to step 2 or step 3.
5. Close out and provide receipt
Only close out when all items have evidence of fix、reject or defer . Use one of the following conclusions:
| Conclusion | Condition |
|---|---|
| approved | Fix passes, rejection reason holds, deferred chain is valid |
| changes requested | There are unverified fixes, omissions, or decisions that do not hold |
| blocked | Missing necessary permissions, environment, input, or follow-up ownership |
修复回执:<approved / changes requested / blocked>。
处理清单:<每条 finding 的决策与结果>
验证:<复现、直接检查、回归和独立复核>
未处理项:<defer 或 blocked 的原因和承接路径>
风险:<仍未覆盖的情形;无则写“无”>
Gate for preventing omissions and fake fixes
- Every finding in the input list has an explicit decision;
- Every fix has diff evidence of code or configuration behavior;
- Direct verification and regression checks are actually run, and failures are not hidden;
- Rejections and deferrals both have reviewable basis;
- Unrelated files or unrelated refactoring are not mixed into the fix commit.
Security boundary
Preserve user confirmation for deletion, overwriting, remote writes, publishing, and expanding fix scope. Do not put local absolute paths, accounts, credentials, or private project context in records or examples.