菜单
Reviews Markdown prose against the pinned agent-style v0.3.5 rules and optionally writes a polished copy beside the source. Use for specs, ADRs, PR bodies, release notes, and technical docs when prose quality or evidence discipline matters.
Turns real agent failures, repeated prompts, team-specific workflows, and durable project lessons into better SDD skills or memory entries. Use when the user asks to create/update/refine skills, extract reusable lessons, improve skill routing, encode team process, or save patterns for future sessions.
Provides the vendored agent-style v0.3.5 prose rule pack as a portable Claude skill. Use when installing, syncing, applying, or auditing SDD Agent-Style support in another project, or when a style-review workflow needs the bundled rules.
Scans Markdown (.md) files for malicious code injection including XSS, prompt injection, script injection, obfuscated payloads, and supply chain attack vectors. Use when auditing .md files for security threats or when the user mentions scanning markdown for malicious content.
Provides .NET and ASP.NET Core patterns for REST APIs, Entity Framework, dependency injection, and middleware. Use when working with C# files (*.cs, *.csproj) or when the user mentions .NET, ASP.NET Core, C#, or Entity Framework.
Designs hybrid cloud architectures connecting on-premises infrastructure with public cloud services. Use when designing systems spanning on-prem and cloud, or when the user mentions hybrid cloud or multi-environment architecture.
Provides microservices design patterns for service decomposition, API gateway, circuit breakers, saga orchestration, and inter-service communication. Use when designing or implementing microservices architecture.
| name | style-review |
| type | workflow |
| description | Reviews Markdown prose against the pinned agent-style v0.3.5 rules and optionally writes a polished copy beside the source. Use for specs, ADRs, PR bodies, release notes, and technical docs when prose quality or evidence discipline matters. |
| argument-hint | [file.md | before.md after.md] |
| user-invocable | true |
| allowed-tools | Read, Glob, Grep, Write, Bash |
| effort | 3 |
| context | main |
| agent | technical-writer |
| when_to_use | Use as an opt-in REVIEW or SHIP gate for important prose artifacts. Do not use for every response, source code, casual chat, or non-English prose unless the user asks for style review. |
Opt-in prose review for SDD artifacts using the portable agent-style v0.3.5
skill bundle. This skill is a second-pass review gate, not a global writing
mode. It does not edit AGENTS.md, CLAUDE.md, or any source document in
place.
.claude/skills/agent-style/references/RULES.md.claude/skills/agent-style/references/UPSTREAM.md.claude/skills/agent-style/references/NOTICE.md.claude/skills/agent-style/references/rule-detectors.md.claude/skills/agent-style/references/revision-prompt.mdUse this skill for English technical prose where clarity, evidence, and review readability matter:
Do not use this skill for routine chat, code, generated logs, or prose where the user's requested voice intentionally overrides formal technical style.
Before any audit, check whether the CLI is available:
agent-style --version
If the command is missing, do not claim style review has run. Report this exact fallback:
style-review not run: `agent-style` CLI is not on PATH. Install with `pip install agent-style` or `npm install -g agent-style`, then rerun `/style-review <file>`.
Do not install dependencies unless the user explicitly asks.
Invocation:
/style-review FILE.md
Read FILE.md and confirm it is prose that fits this skill's scope.
Run the deterministic audit:
agent-style review --audit-only FILE.md
Add semantic judgment for rules the CLI marks as skipped because they need
host-model context: RULE-01, RULE-03, RULE-04, RULE-08, RULE-11, RULE-F, and
RULE-H. Use the bundled agent-style rules and detector reference as the
source of truth.
Report a compact scorecard with per-rule counts and the first few examples.
Ask the user before writing any revised copy:
Produce a polished draft at FILE.reviewed.md?
On yes, compose the revision using the vendored revision prompt and write
only FILE.reviewed.md. Never modify FILE.md.
Re-run the audit on FILE.reviewed.md.
Show before/after scorecard and a diff so the user can merge hunks manually.
Invocation:
/style-review BEFORE.md AFTER.md
Run:
agent-style review --mechanical-only --compare BEFORE.md AFTER.md
Report the per-rule delta. Do not ask for polish and do not write files.
The polished draft must obey these hard constraints:
FILE.reviewed.md.If RULE-H flags unsupported claims, do not invent evidence. Keep the claim flagged or ask the user for the missing source.
When asked "is style-review active?", reply:
style-review active: audit 21 rules from agent-style v0.3.5 (deterministic via CLI; semantic via host for RULE-01, 03, 04, 08, 11, F, H); workflow at .claude/skills/style-review/SKILL.md.