skills.rest
quan0715
quan0715COMMUNITY
Explore all skills by this author →
GitHub

qjudge-quality-gates-owner

Enforce naming, import boundary, and Carbon style quality gates in CI.

31|1|Updated Nov 30, 2025
Search Tags:#architecture#code-quality#lint#naming#ci#quality-gates#carbon-style
One-click install
npx skills add https://github.com/quan0715/QJudge --skill qjudge-quality-gates-owner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qjudge-quality-gates-owner
Source: https://github.com/quan0715/QJudge/tree/main/.codex/skills/qjudge-quality-gates-owner
Command: npx skills add https://github.com/quan0715/QJudge --skill qjudge-quality-gates-owner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Prevent inconsistent naming, architecture boundary violations, and unauthorized Carbon style overrides from entering the codebase by providing executable checks and a rollout policy that can be enforced in PRs and CI.

Core Features & Use Cases

  • Naming lint: Enforces file and directory naming conventions and dot-suffix rules for core/infrastructure artifacts.
  • Architecture lint: Resolves imports and validates allowed layer boundaries under compat and strict policies to detect cross-layer violations.
  • Carbon style gate: Scans changed front-end styles and blocks use of direct Carbon class overrides or !important outside an allowlist.
  • Use Case: Run these checks in PR gates to prevent new violations, run strict reporting in CI for progressive rollout, and eventually flip to hard blocking after stabilization.

Quick Start

Run the naming, architecture, and Carbon style checks in sequence using the provided scripts against the frontend source tree.

Frequently Asked Questions about qjudge-quality-gates-owner

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

FAQPage Schema
How do I enforce naming and architecture quality gates in CI for a frontend codebase?▼

Architecture lint resolves imports to validate allowed layer boundaries under compat and strict policies, detecting cross-layer violations. This mechanism prevents frontend modules from bypassing established architecture boundaries during development and merge.

How do I block unauthorized Carbon style overrides in pull requests?▼

You can run the provided node scripts to lint file and directory names, resolve imports for architecture violations, and execute a shell check for Carbon style restrictions in sequence against your frontend source tree. This enforces naming, architecture, and style checks before merge.

Can I enforce quality gates with a progressive rollout instead of immediately blocking PRs?▼

The architecture lint supports compat and strict policies for import boundary validation. You can start with compat reporting to identify violations and flip to strict mode to hard block cross-layer boundary violations after stabilization.

How do I validate import boundary policies to prevent cross-layer architecture violations?▼

The naming lint enforces file and directory naming conventions, including dot-suffix rules for core and infrastructure artifacts. This prevents inconsistent naming patterns from entering the frontend codebase.

Related Skills

Explore More Software Engineering Skills→
huseyindenizhuseyindeniz
15

security-audit

Analyze TypeScript/JavaScript source code for hardcoded secrets and unsafe patterns.

Community
Advanced
Arry8Arry8
1

github-pr-ready-check

Assess GitHub pull request readiness using gh CLI data.

Community
Intermediate
mizchimizchi
320

frontend-review-hygiene

Run deterministic audit scripts for TypeScript strictness, lint violations, dead code, and duplication.

Community
Intermediate
pax-kpax-k
3

architecture-boundary-enforcer

Enforce and document architecture boundaries using dependency-cruiser, ESLint, import-linter, and custom scripts.

Community
Advanced