to-issues — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited to-issues (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Break a plan into independently pickable tasks using vertical slices (tracer bullets).
The issue tracker and triage label vocabulary should have already been provided to you — if not, run /setup-matt-pocock-skills.
Work with what is already in the conversation context. If the user passes an issue reference (number, URL, or path) as an argument, fetch it from the tracker and read the full body and comments.
If you have not yet explored the codebase, do so to understand the current state of the code. Issue titles and descriptions should use the project's domain glossary and respect ADRs in the area you are touching.
Break the plan into tracer bullet tasks. Each task is a thin vertical slice that goes through ALL integration layers end-to-end, NOT a horizontal slice of a single layer.
Slices can be 'HITL' or 'AFK'. HITL slices require human involvement, e.g. an architectural decision or design review. AFK slices can be implemented and merged without human involvement. Where possible, prefer AFK over HITL.
<vertical-slice-rules>
</vertical-slice-rules>
Present the proposed breakdown as a numbered list. For each slice, show:
Ask the user:
Iterate until the user approves the breakdown.
For each approved slice, publish a new task to the tracker. Use the issue body template below. Apply the needs-triage label so each task enters the standard triage flow.
Publish issues in dependency order (blockers first), so you can reference real issue IDs in the "Blocked by" field.
<issue-template>
Link to the parent task in the tracker (if the source was an existing task; otherwise omit this section).
Brief description of this vertical slice. Describe end-to-end behavior, not a layer-by-layer implementation.
Or "None - can start immediately" if there are no blockers.
</issue-template>
Do NOT close or modify the parent task.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.