code-style-enforcer
Enforce Project Code Style
Teams lose time when code follows different local habits. This skill reviews files against project conventions and recommends consistent style improvements.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "code-style-enforcer" from https://skillstore.io/skills/crazydubya-code-style-enforcer.md and its manifest at https://skillstore.io/api/skills/crazydubya-code-style-enforcer/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.
Test it
Using "code-style-enforcer". A developer asks for a style review of a user service file.
Expected outcome:
- High priority: align method order with nearby service files.
- Medium priority: rename vague temporary variables to domain terms.
- Low priority: make comment format match the project docstring style.
Using "code-style-enforcer". A team wants consistent formatting across a TypeScript module.
Expected outcome:
- The module mixes default and named exports without a clear pattern.
- Imports should follow external, internal, then relative grouping.
- The existing Prettier settings should be treated as the source of truth.
Using "code-style-enforcer". A maintainer asks how to document project style rules.
Expected outcome:
- Create a short style guide with naming, file layout, import order, and comment rules.
- Reference the formatter and linter configuration files from the guide.
- Add examples for the most common review comments.
Security Audit
SafeStatic detections are false positives caused by markdown code fences, inline code, JavaScript template strings, relative import examples, and style guide prose. The skill is limited to Read, Grep, Glob, and Edit and does not contain prompt injection, credential access, network exfiltration, or executable scripts. No semantic security findings were found.
Risk Factors
⚙️ External commands (62)
🌐 Network access (4)
📁 Filesystem access (2)
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.
Copy report link
https://skillstore.io/skills/crazydubya-code-style-enforcer/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/crazydubya-code-style-enforcer?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/crazydubya-code-style-enforcer?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/crazydubya-code-style-enforcer/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/crazydubya-code-style-enforcer.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
CrazyDubya. (2026). code-style-enforcer security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/crazydubya-code-style-enforcer/audits/8BibTeX citation
@techreport{crazydubya-crazydubya-code-style-enforcer-2026,
author = {CrazyDubya},
title = {code-style-enforcer security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/crazydubya-code-style-enforcer/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: "code-style-enforcer security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "CrazyDubya"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/crazydubya-code-style-enforcer/audits/8"
identifiers:
- type: other
value: "skillstore:crazydubya-code-style-enforcer:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Review a Pull Request
Find naming, formatting, and organization issues before a reviewer spends time on style comments.
Standardize a Legacy Module
Compare older files with current project conventions and suggest small, focused cleanup steps.
Create Team Style Guidance
Turn repeated style choices into practical rules for contributors and onboarding documents.
Try These Prompts
Use code-style-enforcer to review this file for naming, formatting, organization, and comment consistency. Return prioritized suggestions.
Use code-style-enforcer to inspect nearby files and style configs, then recommend changes that make this code match the project.
Use code-style-enforcer to review this branch for style-only issues. Separate required consistency fixes from optional readability improvements.
Use code-style-enforcer to identify conflicting conventions across this project and propose a phased plan for consistent style enforcement.
Best Practices
- Start with existing configuration files before proposing new conventions.
- Prioritize changes that improve consistency across similar files.
- Keep style edits separate from behavior changes when possible.
Avoid
- Do not rewrite working code only to satisfy personal style preferences.
- Do not mix formatting changes with unrelated feature work.
- Do not override explicit project conventions without a clear reason.
Frequently Asked Questions
Does this skill replace linters or formatters?
Can it edit files directly?
Which languages does it cover?
How does it choose a style rule?
Can it create a style guide?
Is it useful for pull requests?
Developer Details
Author
CrazyDubyaLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
d11af420e07cd866fe39cfa937efef3223896c06
Maintenance freshness
7/18/2026
Usage
6 downloads · 363 views
File structure