TsukiNi22/ai-utils / skills/routers/style
style
VerifiedRouter for the user's coding style in every language - picks the style skills matching the files (C++, CMake, Python, shell, Lua, JS/TS, C, YAML, comments, docs) to write, format or review code like the user. Invoke manually with /style.
Coding style router
Request given with /style: $ARGUMENTS
Load the skills with the Skill tool (never the other routers: they are manual-only), then write / reformat / review. The request is the text given with
/style (or the latest request; if none, review the uncommitted changes: git diff --stat, git diff).
Skills by file / language
| Files | Skills |
|---|---|
.cpp, .hpp, .tpp, .inl (and .h of a C++ project) | cpp-style + cpp-comments |
.py | python-style + python-comments (new files: python-class) |
any other language: .sh, .lua, .js/.ts, .rs, .go, .c/.h (C), .yml, .json... | coding-style + comments |
| comments of any file (C, CMake, Makefile, shell, Python, Lua, YAML...) | comments |
| new C++ files / classes | cpp-class (layout, header, sections) + the two above |
CMakeLists.txt, *.cmake, *.cmake.in | cmake-style |
| Markdown docs | readme-style |
| HTML docs | html-doc |
| protocol docs (frames, codes, commands: Markdown / PDF / HTML) | protocol-doc |
| commit messages | git-conventions |
| whole project review with a report | audit-quality (PDF) |
Review mode
When xstyle is installed (command -v xstyle), start with xstyle --rtk <paths> -r (compact, made for the assistant; -o /tmp/xstyle.md when a Markdown report is wanted, -S for the
counters): its findings (rule code + severity + fix) are the base of the review, checked and completed by hand;
xstyle --rtk --fix [CODES] applies the fixable ones when the user asks for the fixes.
The review is delivered through report (format asked once, English, audit/ at the repository root) (audit-quality for a whole project).
List the deviations per file with the rule they break (skill + rule), most important first, then propose the
fixes; only apply them if asked. Never change the logic while restyling.
Start the answer with one line listing the loaded skills.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 196k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |