hotfix-8f47a1 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited hotfix-8f47a1 (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.
Apply an urgent fix through a streamlined pipeline that skips the full planning cycle. This skill is for production bugs, security patches, and critical regressions.
[!CAUTION] This is NOT a shortcut for feature work. If the change adds new functionality, changes user-facing behavior, or touches more than ~100 lines, use /plan-feature instead. Hotfixes should be small, focused, and clearly scoped.[!CAUTION] Scope boundary: This skill implements the fix, reviews it, creates a PR, and monitors CI. It covers the full lifecycle for urgent fixes so the user does not need to chain multiple skills.
Ask the user to describe the issue. Gather:
If the user provides a GitHub issue number, fetch it:
gh issue view <number> --json title,body,labels,state,numberPresent a summary and ask the user to confirm this is appropriate for hotfix (not a feature).
main and up to date: git fetch origin
git checkout main
git pull origin mainfix/ branch: git checkout -b fix/<short-description>in-progress label (following AGENTS.md label management rules — remove from any other issue first).Present the root cause analysis to the user before proceeding.
pnpm type-check
pnpm lint
pnpm testPresent:
Wait for user approval before committing.
Commit with conventional commit format:
git add <specific-files>
git commit -m "fix(<scope>): <description>"Run a lightweight review (not the full Review Council):
/security-scanning:security-sast on changed files./ui-design:accessibility-audit on modified components.If the security scan finds Critical or High severity issues in the changed files, present them to the user. Fix any legitimate findings before proceeding.
Activate the Deployment Council only if the fix involves:
If none of these apply, skip to Step 7.
If activated, run the Deployment Council evaluation from .claude/councils/deployment-council.md with all 3 members (Platform Engineer, Security Engineer, QA Lead).
Present the Deployment Council verdict. Wait for user approval.
pnpm type-check && pnpm lint && pnpm format:check && pnpm testAuto-fix formatting issues with pnpm format if format:check fails.
git push -u origin fix/<short-description>.github/PULL_REQUEST_TEMPLATE.md if it exists. Include:Present the PR title and body. Wait for user approval.
gh pr create --title "<title>" --body "<body>" gh run list --branch fix/<short-description> --limit 1 --json databaseId --jq '.[0].databaseId'Then watch:
gh run watch <run-id> --exit-statusPresent the completed hotfix summary:
You completed `/hotfix`. The PR is ready for merge. If there is a related GitHub issue, it will close automatically when the PR merges (if the PR body includes Closes #N).~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.