thkt/formatting-audits
skills/formatting-audits/SKILL.md
Binary Ready/NotReady gate for SOW/Spec. Use when: 設計書レビュー, 実装可否判定, document gate.
$ install --global
skillsauthnpx skillsauth add thkt/dotclaude formatting-auditsInstall 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: Apr 20, 2026, 9:28 AM9.0s1 file scanned
SKILL.md
- name:
- formatting-audits
- description:
- >
- Binary Ready/NotReady gate for SOW/Spec. Use when:
- 設計書レビュー,
- allowed-tools:
- [Read, Grep, Glob]
- agent:
- sow-spec-reviewer
- context:
- fork
- user-invocable:
- false
SOW/Spec Quality Gate
Binary gate: the spec is either ready for CC to implement without asking, or it is not. No numeric score.
Outcome Basis
Goal: every FR / AC produces unambiguous test cases. If CC cannot write a test from a requirement without an escalation, the spec is NotReady.
Judgment rule: "Can I write the Given/When/Then from this requirement right now, with observable assertions?" If no → Blocker.
Priority
| Level | Meaning | Gate | | ----- | ------------------------------------------------------ | ------------- | | P0 | Decision missing or behavior unobservable. CC will escalate | Block (NotReady) | | P1 | Ambiguous but CC can infer with risk of drift | Warn | | P2 | Quality issue, no implementation impact | Info |
Concrete triggers live in validating-specs (check-level) and sow-spec-reviewer
(document-level). The rule for assigning Priority: replay the judgment above on
the specific finding.
Gate
| Condition | Judgment | Action | | ------------------- | --------- | ----------------------------------- | | P0 = 0 | Ready | Proceed to implementation | | P0 ≥ 1 | NotReady | Resolve P0 findings, re-run gate |
P1/P2 findings are reported for visibility. They never block the gate.
Finding Format
Every finding must carry Priority + Fix example. A finding without a Fix example is not actionable and must be rejected as a reviewer error.
| Field | Requirement | | -------- | ----------------------------------------------------- | | Priority | P0 / P1 / P2 | | Location | document:line or section | | CC Impact | What happens when CC reads this (escalates / drifts / ok) | | Fix | Concrete rewrite example, not "clarify this" |
Legacy Format Handling
Documents written before a template extension may lack a newly-added column.
| State | Treatment | | -------------------------------------------- | -------------------------------------------- | | Column exists in table, value empty | Finding per Priority rules (Check 8 etc.) | | Column absent from table structure entirely | Skip column check. Emit P2 "legacy format — column X missing, migrate when convenient" |
Prevents every pre-existing document from being marked NotReady after template changes.
Applies to all column-completeness checks in validating-specs and reviewer agents.
Delegation
| Concern | Skill / Agent |
| ----------------------------------- | ------------------------- |
| AC-FR traceability, consistency | validating-specs |
| Document-level review orchestration | sow-spec-reviewer agent |
Related Skills
thkt/use-cli-herdr
tools
VerifiedTrustedCommunity
Delegate implementation to codex (coder) via the herdr-agentchat plugin and drive a two-pane conversation to completion.
11SKILL.mdUpdated Jul 27, 2026
thkt/scribe
development
VerifiedTrustedCommunity
Extract recurring patterns from past closed PRs/issues and the research findings in workspace/research/, verify them against the latest code, and propose them to docs/wiki/ via PR.
11SKILL.mdUpdated Jul 20, 2026
thkt/dr
development
VerifiedTrustedCommunity
Create Decision Records (DR) in MADR v4 format with auto-numbering.
11SKILL.mdUpdated Jul 15, 2026
thkt/shake
development
VerifiedTrustedCommunity
Detect flaky tests by shaking them — repeated runs under varied order, parallelism, and seed — plus a static smell scan that flags latent flakiness in tests that currently pass. Classify each target as confirmed-flaky, latent-flaky, or stable and fix the root cause without weakening the test. Do NOT use to fix a confirmed single bug (use /fix) or for static-only code review (use /audit).
11SKILL.mdUpdated Jul 13, 2026