codestyle

Detect code style violations and import ordering issues in TypeScript projects.

Updated May 23, 2020
One-click install
npx skills add https://github.com/call1800messiah/The-Eighth --skill codestyle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codestyle
Source: https://github.com/call1800messiah/The-Eighth/tree/main/.claude/skills/codestyle
Command: npx skills add https://github.com/call1800messiah/The-Eighth --skill codestyle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps development teams enforce consistent code style, patterns, and quality across a codebase by detecting violations and generating actionable guidance.

Core Features & Use Cases

  • Detect naming convention violations and import order issues.
  • Enforce Angular and TypeScript patterns and accessibility practices.
  • Auto-fix trivial issues such as import ordering and file naming when safe.
  • Generate detailed compliance reports for audits and CI integration.

Quick Start

Run the codestyle check on your repository to scan all TypeScript files and report style violations.

Frequently Asked Questions about codestyle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce TypeScript and Angular code style rules across a repository?

To enforce TypeScript and Angular code style rules, you can scan your repository to detect naming conventions, import ordering issues, and pattern inconsistencies. This generates structured compliance reports suitable for audits and CI integration.

Can I automatically fix import ordering and file naming issues in TypeScript projects?

Yes, you can automatically fix import ordering and file naming issues in TypeScript projects. The Skill safely auto-fixes trivial styling problems while generating actionable guidance for complex Angular pattern and accessibility violations.

Does this code style checker support whole directory scans for CI integration?

Yes, this code style checker supports whole directory scans for CI integration. It processes TypeScript projects across the entire repository to identify violations and outputs structured compliance reports suitable for automation pipelines.

What is the best way to check Angular pattern compliance and accessibility practices?

The best way to check Angular pattern compliance is to run an automated scan that flags component inconsistencies and accessibility practice violations. This Skill enforces styling patterns and testing compliance, returning detailed actionable guidance.

Why should I use an automated linter for import ordering and naming conventions?

You should use an automated linter for import ordering and naming conventions to ensure consistent code quality across a development team. It detects violations that manual reviews miss and provides structured results that integrate directly into CI workflows.