skills.rest
Jason-hub-star
Jason-hub-starCOMMUNITY
Explore all skills by this author →
GitHub

code-quality-guard

Enforce code quality standards across Python, TypeScript, Go, and Java projects.

Updated Feb 10, 2026
Search Tags:#linting#code-quality#encoding#hardcoding#header-comments#commit-checklist
One-click install
npx skills add https://github.com/Jason-hub-star/GameLab --skill code-quality-guard-jason-hub-star
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-quality-guard
Source: https://github.com/Jason-hub-star/GameLab/tree/main/skills/code-quality-guard
Command: npx skills add https://github.com/Jason-hub-star/GameLab --skill code-quality-guard-jason-hub-star

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent code quality, missing file headers, incorrect encoding, absent documentation, and hard‑coded values lead to maintenance headaches and technical debt.

Core Features & Use Cases

  • File Header Enforcement: Requires a brief comment at the top of new source files.
  • Encoding & Line‑Ending Standards: Provides .editorconfig and .gitattributes configurations for UTF‑8 and LF.
  • CLAUDE.md Folder Convention: Mandates contextual markdown files for AI‑assisted work.
  • Frontend Style Separation: Keeps structure and styling in distinct files or modules.
  • Commit‑Pre Checklist: Validates build, tests, headers, documentation, and hard‑coding before committing.
  • Hard‑coding Policy & Import Rules: Centralises literals and enforces absolute import paths.

Quick Start

Use the code-quality-guard skill to audit your repository and apply the defined code quality rules.

Frequently Asked Questions about code-quality-guard

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

FAQPage Schema
How do I enforce consistent code quality and file header comments across my project?▼

To enforce consistent code quality, you can use a linting skill that mandates brief header comments at the top of new source files and centralizes literals to prevent hardcoding across your codebase.

What is the best way to standardize encoding and line-endings for UTF-8 and LF?▼

Standardizing encoding and line-endings requires setting up .editorconfig and .gitattributes files to enforce UTF-8 and LF standards across all project files consistently.

Does this code quality linting approach work with Python, TypeScript, Go, and Java?▼

Yes, this code quality linting approach applies to Python, TypeScript, Go, and Java, helping teams maintain style separation, import alias configurations, and consistent file hygiene.

How do I validate my commit checklist for builds, tests, and documentation before pushing?▼

To validate your commit checklist, run a pre-commit audit that checks build status, tests, file headers, documentation, and hardcoding policies to ensure codebase readiness.

Do I need CLAUDE.md files in key folders to maintain codebase standards?▼

Yes, you must place CLAUDE.md files in key folders to provide contextual markdown documentation for AI-assisted work and satisfy the codebase standard requirements.

What are the limitations of enforcing hardcoding policies and import rules?▼

Enforcing hardcoding policies and absolute import paths requires strict adherence to centralizing literals and configuring import aliases, which may require refactoring existing non-compliant code.

Related Skills

Explore More Software Engineering Skills→
vm-wylburvm-wylbur
1

new-file

Validate file necessity and generate language-specific headers before creating new files.

Community
Basic
DevelonautDevelonaut
3

pre-commit

... (please answer in English only, and in fewer than 200 characters)

Community
Intermediate
NeKon69NeKon69
1

Plugin.lspsaga API Reference

Generate an API reference index for the lspsaga.nvim plugin from Lua source files.

Community
Basic
georgekhananaevgeorgekhananaev
27

code-quality

Enforce cross-language code quality standards across TypeScript, Python, Go, and Rust.

Community
Advanced