← ClaudeAtlas

skillsaw-release-readylisted

Audit skillsaw for release readiness — test new rules against real repositories, audit core architectural dimensions, independently verify proposed fixes, and ship improvements in clean, focused batches. Use before cutting a release.
stbenjam/skillsaw · ★ 73 · AI & Automation · score 90
Install: claude install-skill stbenjam/skillsaw
<!-- Source paths below are repo-root-relative references, not links navigable from this skill's directory. --> <!-- skillsaw-disable content-unlinked-internal-reference --> # skillsaw Release Ready Ensure skillsaw is rock-solid before every release. This skill orchestrates parallel subagent reviews to test newly added rules against real-world repositories, audits key codebase dimensions, and ships vetted improvements in clean batches of up to 10 commits per PR. Reviewers evaluate every finding using three core questions: 1. **Does it affect common usage?** Prioritize findings that developers will frequently encounter on real projects. 2. **Is it accurate?** Guard against false positives on files that upstream tools accept. 3. **Is it helpful and high-signal?** Ensure rules provide clear value without unnecessary noise. ## Step 1: Establish scope Identify what has changed since the last release tag: ```bash git fetch --tags git diff --name-status v<last>..HEAD -- src/skillsaw/rules/builtin/ | grep -E '^[AM]' git log --merges --format=%s v<last>..HEAD gh pr view <n> --json title,body # review previous release-readiness PRs ``` List new rule IDs, modified rules, and fixes that have already landed so reviewers can focus on unresolved areas. ## Step 2: Set up the audit workspace - Use `~/tmp/skillsaw-audit/` for working files (`corpus/`, `reports/`, `briefs/`, `work/<agent>/`). - Shallow-clone a representative corpus of real repositories into `corpus/` (see [corpus](r