# Standardize Deliverable Formatting

Generated work often mixes styles, spacing, and structure. This skill applies consistent formatting so deliverables are easier to review and reuse.

## Install

```bash
npx skillstore add abejitsu/format-standardize
```

## Metadata

- Status: approved
- Slug: abejitsu-format-standardize
- Skillstore revision: r1
- Version status: missing
- Tree hash: e3cb3f3c6bfada59120c45b5b1cdbedde417fe94912f4862bc4183c0fc94c938
- Author: AbeJitsu
- GitHub username: AbeJitsu
- License: MIT
- Repository: https://github.com/AbeJitsu/Game-Settings-Panel/tree/main/.claude/skills/format-standardize
- Ref: 9f22d902a4190b1e33cced8a68441beb8e612f59
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/abejitsu-format-standardize
- Manifest: https://skillstore.pages.dev/api/skills/abejitsu-format-standardize/manifest

## Capabilities

- Reviews generated deliverables for formatting consistency.
- Loads project formatting standards through StandardsRepository when available.
- Applies code style checks for indentation, naming, spacing, imports, and line length.
- Standardizes documentation headings, lists, code blocks, links, and tables.
- Returns standards used, changes made, the formatted deliverable, and validation notes.

## Use Cases

- Prepare Code For Review: Normalize indentation, spacing, names, imports, and semicolons before a reviewer checks the change.
- Polish Technical Documentation: Standardize headings, lists, code blocks, links, and tables before publishing a guide or specification.
- Unify Generated Deliverables: Apply one style across mixed AI-generated code, explanations, validation notes, and examples.

## Prompt Templates

### Format A Draft

```
Standardize this deliverable for consistent headings, spacing, lists, and punctuation. Preserve the meaning and return the polished version.
```

### Apply Project Style Rules

```
Format this work using our project standards. Use two-space indentation, consistent Markdown headers, sorted imports, and concise validation notes.
```

### Standardize Mixed Output

```
Review this mixed deliverable. Standardize the code, documentation, examples, and change summary while keeping the original behavior intact.
```

### Prepare Release-Ready Output

```
Perform a final formatting pass for release. Report standards used, changes made, the final deliverable, and any remaining formatting risks.
```

## Limitations

- Does not provide a full formatter implementation.
- Depends on available project standards or clear user instructions.
- Does not verify that code behavior remains correct after broader edits.
- Does not include automated tests or formatter integrations itself.

## Best Practices

- Provide the style guide or formatter preference before using the skill.
- Ask the skill to preserve behavior while changing formatting only.
- Review final output for domain accuracy after formatting.

## Anti Patterns

- Using the skill for risky logic refactors instead of formatting cleanup.
- Running the skill without specifying important project style constraints.
- Treating visual polish as a substitute for tests or expert review.

## Security Audit

- Audited at: 2026-07-07T20:14:13.755\+00:00
- Summary: All eight static external command findings are false positives caused by Markdown code fences, inline path formatting, and JavaScript examples in SKILL.md. I found no prompt injection, data exfiltration intent, or hidden command execution evidence in the reviewed file.

## Stats

- Views: 191
- Downloads: 10
- Favorites: 0
- Popularity score: 0