bugfix-crate
Fix the findings recorded in a crate issue file one at a time, with failing test first, minimal fix second, full crate verification third, and issue-file status updates after each successful fix. Use for Rust crate issue lists that already exist and need disciplined sequential repair.
What this skill does
<EXTREMELY-IMPORTANT> This skill is a strict red-green-refactor repair loop. Non-negotiable rules: 1. Fix one finding at a time. 2. For behavioral bugs, write the failing regression test before the fix. 3. Run crate tests and clippy after every fix. 4. Do not mark a finding fixed without the required verification. 5. Use the `rust` skill for crate-specific coding conventions before changing Rust code. </EXTREMELY-IMPORTANT> # bugfix-crate ## Inputs - `$issues_file`: Path to the crate findings file ## Goal Work through a crate issue file sequentially and leave behind: - a verified fix for each resolved finding - regression coverage for each behavioral fix - a passing crate test suite - an updated issue file showing what was fixed, deferred, or rejected as not-a-bug ## Step 0: Establish the baseline Before editing: - read the entire issue file - determine the target crate name and path - invoke `rust` for relevant conventions - read crate-local `CLAUDE.md` or testing guidance if present - run baseline `cargo test -p <crate>` - run baseline `cargo clippy -p <crate> -- -D warnings` **Success criteria**: The crate, issue file, and baseline state are explicit before the first fix. ## Step 1: Process one finding at a time For each unresolved finding: - read the cited file and surrounding context - determine whether it is behavioral, API, dead-code, doc-only, deferred, or not-a-bug - if it is a behavioral or API fix, write the failing test first - verify the test fails before changing the implementation Do not batch findings. **Success criteria**: Each finding has a concrete resolution path before any fix lands. ## Step 2: Apply the smallest correct fix Make the minimum code change that addresses the root cause. Rules: - do not batch adjacent refactors - do not weaken existing tests - do not hide warnings with `#[allow(...)]` - if you uncover another real bug in the touched area, fix it in the same pass and add it to the issue file **Success criteria**: The fix addresses the root cause without broad collateral edits. ## Step 3: Verify and mark status After each fix: - run `cargo test -p <crate>` - run `cargo clippy -p <crate> -- -D warnings` - update the issue file: - `**[FIXED]**` for verified fixes - `Deferred: <reason>` for real out-of-scope fixes - `Not a bug: <reason>` for invalid findings Do not mark a finding fixed before the verification pass completes. **Success criteria**: The issue file and crate state stay in sync after every finding. ## Step 4: Finish only when the issue file is resolved At the end: - confirm every finding has a terminal status - confirm the crate still passes tests and clippy - summarize resolved, deferred, and rejected findings **Success criteria**: The issue file is fully triaged and the crate is green. ## Guardrails - Do not use worktree agents for same-crate fixing. - Do not run this skill proactively; it is explicit-user-only. - Do not mark behavioral bugs fixed without regression coverage. - Do not replace a real fix with comments, warnings, or documentation. - Do not batch multiple findings in one verification loop. ## Output Contract Report: 1. crate and issue file processed 2. baseline test and clippy state 3. per-finding outcome 4. final test and clippy state 5. any newly discovered findings added during repair
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.