do-issue — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited do-issue (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.
If the user asked you to implement a specific issue by number, open that issue's description file in ./issues (files start with the issue number). If the user asked you to implement the next issue, list all files in ./issues (they are ordered) and start with the first one marked as ready-for-agent in its head label. Just use head on the issue file to determine its status.
You are free to gather additional context from the repo. Avoid the ./prd directory and any issues other than your current one in ./issues.
Only implement this one issue.
Each issue has a set of acceptance criteria you need to fulfill in order for the issue to be marked as implemented.
When you're done with the issue mark it as implemented in ./issues.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.