A workflow that automatically fixes mechanical style issues and runs the project's full verification checks, including tests, linting, dependency checks, and code-quality checks.

Use it before releases or after code changes to format files, run the verification gate, and report failures.

It finds problems that a basic check may omit and prevents release work from continuing with a failing build.

How CinqueIzumi/Softcover configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to CinqueIzumi/Softcover. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/CinqueIzumi/Softcover/main/.claude/skills/style-check/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/CinqueIzumi/Softcover

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cinqueizumi/softcover/style-check/github.svg)](https://agentmods.dev/skills/cinqueizumi/softcover/style-check)

Your own site

<a href="https://agentmods.dev/skills/cinqueizumi/softcover/style-check"><img src="https://agentmods.dev/badge/skills/cinqueizumi/softcover/style-check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cinqueizumi/softcover/style-check"><img src="https://agentmods.dev/badge/skills/cinqueizumi/softcover/style-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 380 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00033	$0.00380
Opus 5.5	$0.00013	$0.00152
Sonnet 5.5	$0.00007	$0.00076
Haiku 4.5	$0.00003	$0.00038

Measured 12d ago against content hash bfd02f7c023d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

style-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/style-check/SKILL.md · 19 lines

What it actually says

Auto-fix the mechanizable style issues, then run the full set of checks — including the buildHealth gate that ./gradlew check omits — and report.

Steps:

Use the Bash tool to run ./gradlew ktlintFormat lintFix to auto-fix the mechanizable layout and lint issues. This may modify files.
Use the Bash tool to run the full gate: ./gradlew check buildHealth. This covers lint, styleCheck (ktlint plus type-resolved detekt), unit tests, checkModuleGraph, and iOS compilation of every KMP module (all via check), plus dependency analysis (buildHealth). Note: the iOS-compile gate only runs on macOS (Kotlin/Native iOS compilation is unavailable elsewhere), so run release prep on a Mac to exercise it. Gradle calls are rewritten to scripts/gradle-quiet.sh, which prints a short summary (result, failed tasks, compiler errors, failing tests, style findings) and the path of the full log. Read the summary and grep that log for detail; do not re-run the gate verbose.
If the gate fails, surface the failing task(s) and the relevant output to the user. Do not attempt non-mechanical fixes automatically — check and buildHealth failures are blocking and need a human decision.
Report which auto-fixes were applied (mention that git diff is available to review them) and the gate result. Treat check/buildHealth failures, including styleCheck findings, as blocking.

Do not create a commit.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago Changed · -1 tokens per session bfd02f7c023d
1mo ago Changed · +2 lines aed28367707a
2mo ago First seen · 17 lines · 34 tokens per session scan A 21cc726c64f9

Subscribe to this mod's changes

style-check is a skill published in the GitHub repository CinqueIzumi/Softcover (16 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 380 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

Softcover: Skill for Claude Code