# Audit Code Style and Maintainability

Teams need code that is correct, readable, maintainable, and aligned with project standards. This skill guides style review, safe refactoring, documentation checks, and quality reporting after functionality is validated.

## Install

```bash
npx skillstore add dnyoussef/style-audit
```

## Metadata

- Status: approved
- Slug: dnyoussef-style-audit
- Skillstore revision: r1
- Version status: missing
- Tree hash: 0afdeeb72a450b27f39f1fb7ae279cfd69e39c38a7efb70a1ef0e959db7762c9
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/style-audit
- Ref: 72d5025b022c77f7a51bdf5c1637c689c80e89d1
- 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
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dnyoussef-style-audit
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-style-audit/manifest

## Capabilities

- Runs language-appropriate linting and formatting checks when tools are available.
- Reviews naming, decomposition, complexity, documentation, error handling, security, and performance.
- Prioritizes style issues by risk, readability, maintainability, and user impact.
- Applies automated formatting fixes before manual refactoring when appropriate.
- Rewrites code for clarity while preserving verified behavior through tests.
- Produces reports with findings, refactoring notes, remaining issues, and quality metrics.

## Use Cases

- Prepare a Pull Request: Improve naming, formatting, documentation, and error handling before asking teammates for review.
- Standardize Inherited Code: Audit working code against team conventions and create a prioritized cleanup plan.
- Enforce CI Quality Gates: Align linting, formatting, type checks, and security review with CI expectations.

## Prompt Templates

### Review Style Issues

```
Audit the selected files for style, readability, naming, and documentation issues. Report findings before making changes.
```

### Fix Safe Formatting Problems

```
Run available linting and formatting checks on this project. Apply safe automated fixes, then summarize what changed.
```

### Refactor for Maintainability

```
After confirming tests pass, refactor complex functions for clarity. Preserve behavior and explain the tests that support each change.
```

### Create a CI Style Plan

```
Audit the codebase against our style goals and CI checks. Propose phased fixes, tool configuration changes, and remaining risks.
```

## Limitations

- It depends on available linters, test suites, and project configuration.
- It should run after functionality validation, not replace it.
- It may need team guidance when multiple style choices are valid.
- It cannot prove security or performance without relevant tests and runtime evidence.

## Best Practices

- Run functionality tests before and after each significant style change.
- Provide team style guidelines and lint configurations before the audit.
- Separate automated formatting, manual refactoring, and documentation updates into reviewable changes.

## Anti Patterns

- Using the skill to change untested behavior during a style cleanup.
- Treating default linter settings as team standards without review.
- Applying large refactors without explaining risk, tests, and remaining issues.

## Security Audit

- Audited at: 2026-07-06T11:42:19.861\+00:00
- Summary: All 11 static findings are false positives caused by quality-review prose and DOT graph labels. I found no prompt injection, credential access, network behavior, command execution, or data exfiltration intent in the reviewed files.

## Stats

- Views: 192
- Downloads: 13
- Favorites: 0
- Popularity score: 0