Parameterize the Brief, Verify the Execution

You keep asking for the same issue workflow: read the requirements, locate the change, implement it and run the relevant checks. A parameterized skill can save you from rewriting that brief.

A manually invoked skill can use disable-model-invocation: true and $ARGUMENTS, so /fix-issue 1234 supplies the issue number to its instructions. The skills documentation describes those controls.

This makes the instruction reusable. It does not turn the model's interpretation into a deterministic function or prove every step ran. Keep explicit permissions and approval boundaries for commits, pull requests and external actions.

Put repeatable mechanical checks in scripts, retain their output, and inspect the resulting diff. A good skill supplies a consistent task contract; the evidence tells you whether this particular execution met it.