Menu

Individual skill

fix

When explicitly invoked with a software defect or unwanted behavior, translate the natural-language report and repository evidence into one compact repair contract, explain it plainly, then fix it in one approved shot. Never invoke implicitly.

plugins/grapefruit0205/click/skills/fix/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Fix

Use `$fix` only when the user explicitly selects it. Do not infer activation from words such as “bug,” “broken,” or “fix,” and do not promise a native `/fix` command. `$fix` intentionally selects Click's Guarded repair workflow. Read Click's [operating modes](../click/references/modes.md) for the exact arm, bypass, cancel, and resume rules, and the [Guarded mode workflow](../click/references/guarded-mode.md) for the contract, approval, and execution rules it shares.

Trace the reported symptom to the narrowest owning behavior, relevant state, public contract, and focused evidence. Keep confirmed repository evidence separate from hypotheses. Resolve ordinary repair tactics yourself and expose only consequential assumptions in the contract instead of asking serial implementation questions.

Use Click's shared [contract format and approval lifecycle](../click/references/directive-format.md) and [verification profiles](../click/references/verification-profiles.md). Stage the repair JSON once, keep `plain_language` digest-bound, capture its `contract_id` from `CLICK_CONTRACT_ID`, and present the exact Hook-generated easy contract once without independently summarizing it. Keep the original JSON hidden unless requested, and treat viewing it as neither approval nor a replacement stage. Offer approval, requested changes, cancellation, or original-contract viewing, then stop without editing. Only after explicit approval in a later user turn, pass that id—never resend the JSON.

Then follow the shared [anti-loop policy](../click/references/anti-loop-policy.md) and [structured capability protocol](../click/references/capability-protocol.md). Repair continuously inside the approved semantic boundary, collect each assigned completion source once on the final relevant revision, and stop when the repair is proven. Pause only for missing authority, an uncovered irreversible or paid action, or a required change to the approved semantic contract.