code-quality-guard

Name: code-quality-guard
Availability: InStock
Author: kimjuyoung1127

Enforce header comments, UTF-8 LF encoding, CLAUDE.md conventions, and pre-commit checks.

Updated Feb 10, 2026

Search Tags:#linting #pre-commit #code-quality #encoding #ci-cd #coding-standards #style-separation

Ready to run

npx skills add https://github.com/kimjuyoung1127/GameLab --skill code-quality-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-quality-guard
Source: https://github.com/kimjuyoung1127/GameLab/tree/main/skills/code-quality-guard
Command: npx skills add https://github.com/kimjuyoung1127/GameLab --skill code-quality-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining uniform code hygiene across projects is challenging without enforced standards. This Skill defines and enforces header comments, encoding/line endings, CLAUDE.md folder conventions, commit pre-checks, style separation, and hardcoding policies to keep codebases clean and predictable.

Core Features & Use Cases

Enforces at-a-glance documentation and adherence to coding standards across languages through header comments and encoding rules.
Guides new projects and teams on applying CLAUDE.md conventions, pre-commit checklists, and structured style separation to improve collaboration and maintainability.
Use Case: When starting a new project, run the code-quality-guard setup to initialize rules and validate ongoing contributions.

Quick Start

Run the code-quality-guard checklist on a new project to initialize and enforce all 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 coding standards and consistent code quality across my project?▼

You can enforce coding standards by applying a comprehensive code hygiene policy that mandates header comments, UTF-8 with LF encoding, pre-commit checks, and style separation to keep your codebase clean and predictable.

What should be included in a pre-commit checklist to maintain project hygiene?▼

A pre-commit checklist for project hygiene should validate header comment conventions, verify UTF-8 with LF line endings, ensure structure and style separation, and confirm no hardcoded secrets exist in the codebase.

How do I set up CLAUDE folder conventions for a new development project?▼

To set up CLAUDE folder conventions, initialize a CLAUDE.md file within your project folders to document directory standards, and run a code-quality-guard checklist to validate ongoing contributions against these rules.

Does enforcing encoding and line ending standards improve team collaboration?▼

Enforcing UTF-8 with LF encoding and line endings improves team collaboration by preventing cross-platform formatting conflicts, ensuring that file headers and structure remain predictable across all ongoing development workflows.

What is the best way to prevent hardcoded secrets in a CI-CD pipeline?▼

The best way to prevent hardcoded secrets in a CI-CD pipeline is to enforce a strict no-hardcoding policy through pre-commit checks, ensuring all sensitive data is externalized before code integration.

When should I apply header comments and style separation in my codebase?▼

You should apply header comments and style separation during new project startups and ongoing development workflows to enforce at-a-glance documentation and maintain clear boundaries between code structure and styling.