Skills style-audit
📦

style-audit

Content revision r1 Safe

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.

Supports: Claude Codex Code(CC)
🥉 79 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "style-audit" from https://skillstore.io/skills/dnyoussef-style-audit.md and its manifest at https://skillstore.io/api/skills/dnyoussef-style-audit/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/dnyoussef-style-audit.md Signed manifest GET /api/skills/dnyoussef-style-audit/manifest Signed lockfile GET /api/skills/dnyoussef-style-audit/lockfile

Test it

Using "style-audit". Audit a JavaScript feature branch before review.

Expected outcome:

  • Found inconsistent naming, missing error handling, and two long functions.
  • Applied formatting fixes and proposed a smaller refactor for the complex functions.
  • Recommended adding a regression test before changing validation logic.

Using "style-audit". Review Python service code after functionality tests pass.

Expected outcome:

The audit reports linting issues, missing type hints, weak docstrings, and one inefficient loop. It suggests ordered fixes and verification steps.

Using "style-audit". Create a style report for a team handoff.

Expected outcome:

  • Summarized overall code quality and the highest-impact style risks.
  • Grouped findings by formatting, naming, complexity, documentation, and error handling.
  • Listed deferred issues with effort estimates and recommended priority.

Security Audit

Safe
v8 • 7/6/2026 Open versioned report

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.

2
Files scanned
337
Lines analyzed
0
Review items
0
False positives ignored
No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/dnyoussef-style-audit/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/dnyoussef-style-audit/security.svg)](https://skillstore.io/skills/dnyoussef-style-audit?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/dnyoussef-style-audit?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dnyoussef-style-audit/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/dnyoussef-style-audit.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

DNYoussef. (2026). style-audit security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dnyoussef-style-audit/audits/8

BibTeX citation

@techreport{dnyoussef-dnyoussef-style-audit-2026, author = {DNYoussef}, title = {style-audit security audit report (audit version 8)}, institution = {Skillstore}, year = {2026}, number = {8}, url = {https://skillstore.io/skills/dnyoussef-style-audit/audits/8}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "style-audit security audit report (audit version 8)" version: "unspecified" type: report authors: - name: "DNYoussef" date-released: "2026-07-06" url: "https://skillstore.io/skills/dnyoussef-style-audit/audits/8" identifiers: - type: other value: "skillstore:dnyoussef-style-audit:audit:8" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
70
Community
91
Spec Compliance

What You Can Build

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.

Try These Prompts

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.

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.

Avoid

  • 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.

Frequently Asked Questions

Does this skill replace code review?
No. It removes style noise and prepares clearer code, but human review should still evaluate design and intent.
Can it edit code directly?
Yes, when asked. It prioritizes safe automated fixes and should verify behavior with tests.
Which languages does it support?
It is language-agnostic. It recommends common tools such as ESLint, Prettier, Black, flake8, pylint, and mypy when relevant.
When should I use it?
Use it after functionality is validated and before pull requests, handoff, or CI quality gate work.
Will it enforce my team style guide?
Yes, if you provide the guide or configuration. Without it, the skill uses general maintainability practices.
Can it find security issues?
It includes secure coding review for input validation, sensitive data handling, and common attack surfaces. It is not a full penetration test.

Developer Details

Author

DNYoussef

License

MIT

Skillstore revision

r1

Version notice

The author did not declare a version.

Repository

https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/style-audit

Ref

72d5025b022c77f7a51bdf5c1637c689c80e89d1

Maintenance freshness

7/23/2026

Usage

10 downloads · 192 views

File structure

📄 SKILL.md

📄 style-audit-process.dot