agent-style

$npx mdskill add tranhieutt/software_development_department/agent-style

Vendors agent-style v0.3.5 prose rules as a portable Claude skill.

  • Installs, syncs, or audits Agent-Style support in another project.
  • Depends on Read, Glob, Grep, and Bash tools.
  • Checks for required skill and rules files to verify availability.
  • Provides bundled rules and references for style-review workflows.

SKILL.md

.github/skills/agent-styleView on GitHub ↗
---
name: agent-style
type: workflow
description: "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."
argument-hint: "[install-check | audit FILE.md | compare BEFORE.md AFTER.md]"
user-invocable: true
allowed-tools: Read, Glob, Grep, Bash
effort: 2
context: main
agent: technical-writer
when_to_use: "Use when Agent-Style must travel with .claude/skills during SDD apply/sync, or when an agent needs the pinned rule pack without relying on a repository-level .agent-style directory."
---

# Agent Style

Portable SDD wrapper for the vendored `agent-style` v0.3.5 rule pack.

This skill exists so Agent-Style support moves with `.claude/skills/` when SDD
is applied to another project. It does not enable global writing style, does not
edit `AGENTS.md` or `CLAUDE.md`, and does not replace `style-review`.

## Bundled Source

- Rules: `references/RULES.md`
- Upstream pin: `references/UPSTREAM.md`
- Attribution: `references/NOTICE.md`
- Detector notes: `references/rule-detectors.md`
- Revision prompt: `references/revision-prompt.md`

Retain `references/NOTICE.md` when copying or redistributing this skill.

## Install Check

When asked whether Agent-Style is available in a target project, verify:

1. `.claude/skills/agent-style/SKILL.md` exists.
2. `.claude/skills/agent-style/references/RULES.md` exists.
3. `.claude/skills/style-review/SKILL.md` points to the bundled agent-style
   references, not a required repository-level `.agent-style/` directory.

If the target project still uses `.agent-style/` directly, migrate by copying
this entire skill folder and updating `style-review` source paths.

## CLI Check

For deterministic audits, check:

```bash
agent-style --version
```

If missing, report:

```text
agent-style deterministic audit unavailable: `agent-style` CLI is not on PATH. Bundled rules remain available for semantic review through `.claude/skills/agent-style/references/`.
```

Do not install dependencies unless the user asks.

## Audit Routing

For file review, use `style-review`. This skill supplies the portable rule pack;
`style-review` supplies the review workflow, audit command, polish invariants,
and completion evidence.

Use this skill directly only for:

- Checking whether Agent-Style travels with SDD apply/sync.
- Reading the pinned rules or upstream metadata.
- Migrating an older `.agent-style/`-based repo into `.claude/skills`.

More from tranhieutt/software_development_department

SkillDescription
agent-healthReads production/traces/agent-metrics.jsonl and displays a per-agent performance summary table for the current or a specified session. Highlights agents with high error rates or OPEN circuit breaker state.
angular-best-practicesProvides Angular best practices for components, modules, services, and reactive patterns. Use when working with Angular TypeScript files, component templates, NgModules, RxJS observables, or when the user mentions Angular, ng, or Angular CLI.
annotateRecords unexpected API behaviors, undocumented caveats, version bugs, or non-obvious workarounds into .claude/memory/annotations.md. Use immediately when an undocumented behavior or surprising caveat is discovered during development.
aws-serverlessProvides AWS serverless architecture patterns for Lambda, API Gateway, DynamoDB, SQS, and SAM/CDK. Use when working with AWS serverless files (serverless.yml, CDK stacks) or when the user mentions Lambda, API Gateway, serverless, or AWS SAM.
backend-architectDesigns scalable backend architectures covering microservices, event-driven systems, API gateways, and data stores. Use when designing a backend system or when the user mentions backend architecture, scalability, or distributed systems.
cloud-run-puppeteerDeploys Puppeteer browser automation on Google Cloud Run with Docker. Use when running headless browser tasks on Cloud Run, or when the user mentions Cloud Run, Puppeteer, headless Chrome, or serverless browser automation.
codex-sddAdapts SDD for Codex while preserving Claude Code behavior. Use when working in Codex, setting up Codex compatibility, mapping Claude tools to Codex tools, or explaining how SDD should run outside Claude Code.
database-architectDesigns relational and NoSQL database schemas, indexing strategies, migration plans, and data modeling patterns. Use when designing a database or when the user mentions database architecture, schema design, or data modeling.
db-reviewReviews database schemas, queries, and migrations for correctness, performance, security, and best practices. Use when reviewing SQL migration files or when the user mentions database review, schema review, or query audit.
deep-interviewConducts a structured technical deep-dive to gather detailed requirements, constraints, and decisions from the user. Use when starting a complex feature or when the user wants to be asked structured clarifying questions before implementation.