Repair Rust crate review findings sequentially with regression tests and Clippy verification.
npx skills add https://github.com/ulpi-io/skills --skill bugfix-crate
Please help me install this Agent Skill. Skill: bugfix-crate Source: https://github.com/ulpi-io/skills/tree/main/bugfix-crate Command: npx skills add https://github.com/ulpi-io/skills --skill bugfix-crate
This Skill turns recorded Rust crate review findings into verified fixes while keeping regression tests, validation results, and issue-file statuses synchronized.
Ask the bugfix-crate skill to work through the findings in the specified Rust issue file sequentially and verify every fix.
High-intent search queries and answers about installing and using this skill.
To fix Rust crate review findings, process each issue sequentially: write a failing regression test for behavioral or API bugs, apply the smallest correct fix, run the full crate test suite and strict cargo clippy, then update the issue file status to fixed, deferred, or invalid.
Triage Rust crate findings by evaluating each issue individually to classify it as a behavioral bug, API issue, dead code, documentation finding, or deferred work. Repair valid findings with regression tests and cargo clippy verification, or mark invalid findings as not a bug.
Yes, strict cargo clippy verification is required after every individual Rust crate bug fix. You must also run the full crate test suite to ensure no regressions and confirm adherence to Rust-specific coding conventions before updating the issue file resolution status.
No, Rust crate review findings must be repaired sequentially one at a time rather than batching changes. This ensures each fix gets its own failing regression test, the smallest correct code modification, and full cargo test and cargo clippy validation before moving to the next.
Regression testing for Rust crate behavioral bugs follows a red-green approach: write a failing test reproducing the bug, then apply the smallest correct fix to make it pass. The full crate test suite is run afterward to verify no other regressions were introduced.
Mark a Rust crate finding as deferred when the issue represents deferred work that cannot be immediately resolved. Findings are marked as fixed only after regression tests and cargo clippy verification pass, or as not a bug when the finding is evaluated as invalid.
hiromimaAutomate cargo build, test, clippy, and fmt across the Miyabi workspace.
devrelaicomVerify ledger claims by tracing them to Rust source files and paths.
aniruddh2003Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.
LazyNinja435Enforce the Red-Green-Refactor cycle for verified production code.
