rafaie/spec-linter
skills/spec-linter/SKILL.md
Review a work item documentation folder for clarity, testability, and completeness before implementation.
$ install --global
skillsauthnpx skillsauth add rafaie/codex_home spec-linterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 5, 2026, 6:24 AM320.6s1 file scanned
SKILL.md
- name:
- spec-linter
- description:
- Review a work item documentation folder for clarity, testability, and completeness before implementation.
- Read the target work item folder
spec/features/<work-id>-<slug>/and project conventions fromAGENTS.md.<work-id>must useS-<stream>-<nnn>(example:S-core-001) for new work.- For legacy single-file specs, read the matching file under
spec/features/.
- Check for:
feature.md: clear problem statement, scope/non-scope, testable acceptance criteria, inputs/outputs, ADR linkageimplementation.md: initial implementation plantest-plan.md: unit/integration/e2e/edge/smoke plantest-results.md: command/result placeholders and evidence sectionstatus.md: current status, owner, next action, blockersevidence/README.md: evidence index with smoke artifact/summary placeholders- Smoke placeholders: scenario, fixture, pass/fail mode, runtime budget, artifact path
- Docstring expectations: API-facing work mentions Google-style docstrings or explicitly explains why no docstring updates are needed
- Legacy single-file specs: equivalent sections are present
- Produce a short “Spec Gaps” list, then either:
- Propose edits, or
- Apply edits directly if the user asks.
- End by recommending the next skill (usually
write-testsorimplement-feature).
Related Skills
rafaie/write-tests
testing
VerifiedTrustedCommunity
Add or improve tests based on a work item folder's acceptance criteria and test plan.
1SKILL.mdUpdated May 5, 2026
rafaie/test-runner
testing
VerifiedTrustedCommunity
Run quick/full checks consistently, include smoke, and summarize failures into actionable buckets.
1SKILL.mdUpdated May 5, 2026
rafaie/test-plan
testing
VerifiedTrustedCommunity
Create a work item test plan from acceptance criteria and add it to the work item docs.
1SKILL.mdUpdated May 5, 2026
rafaie/smoke-test
testing
VerifiedTrustedCommunity
Run a real entrypoint smoke test, emit required artifacts, classify failures, and recommend the next action.
1SKILL.mdUpdated May 5, 2026