speckit-git-validate — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited speckit-git-validate (Agent Skill) and scored it 83/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 4 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 4 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.
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.
Validate that the current Git branch follows the expected feature branch naming conventions.
git rev-parse --is-inside-work-tree 2>/dev/null [specify] Warning: Git repository not detected; skipped branch validationGet the current branch name:
git rev-parse --abbrev-ref HEADThe branch name must match one of these patterns:
^[0-9]{3,}- (e.g., 001-feature-name, 042-fix-bug, 1000-big-feature)^[0-9]{8}-[0-9]{6}- (e.g., 20260319-143022-feature-name)If on a feature branch (matches either pattern):
✓ On feature branch: <branch-name>specs/:specs/<prefix>-* where prefix matches the numeric portionspecs/<prefix>-* where prefix matches the YYYYMMDD-HHMMSS portion✓ Spec directory found: <path>⚠ No spec directory found for prefix <prefix>If NOT on a feature branch:
✗ Not on a feature branch. Current branch: <branch-name>Feature branches should be named like: 001-feature-name or 20260319-143022-feature-nameIf Git is not installed or the directory is not a Git repository:
SPECIFY_FEATURE environment variable as a fallback~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.