skills.rest
GantisStorm
GantisStormCOMMUNITY
Explore all skills by this author →
GitHub

code-quality

Run type checking and linting on staged code changes via start.sh.

6|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/GantisStorm/claude-code-pair-planning-framework --skill code-quality-gantisstorm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-quality
Source: https://github.com/GantisStorm/claude-code-pair-planning-framework/tree/main/codex-swarm/skills/code-quality
Command: npx skills add https://github.com/GantisStorm/claude-code-pair-planning-framework --skill code-quality-gantisstorm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides quick access to code quality checks to ensure code health after edits, before commits, or on demand.

Core Features & Use Cases

  • Full checks: type checking, linting, and static analysis in one command.
  • Selective checks: run typecheck or lint individually.
  • Workflow: integrate into CI or local development to catch issues early.

Quick Start

Run the full check with ./start.sh check, or run lint with ./start.sh lint.

Frequently Asked Questions about code-quality

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

FAQPage Schema
How do I run code quality checks on my local repository?▼

Code quality checks run via `./start.sh check` to perform type checking, linting, and static analysis on staged changes in your local repository. This command executes all checks in one pass to catch issues before commit.

Can I run type checking and linting separately?▼

Yes, you can run selective checks: use `./start.sh typecheck` for type checking alone or `./start.sh lint` for linting only. This lets you focus on specific issue types during development.

Does this Skill automatically fix linting issues?▼

The Skill includes an auto-fix workflow via `./start.sh lint-fix`, which applies automatic corrections to linting violations. Iterative verification ensures all issues are addressed after running fixes.

What environment do I need to run these code quality checks?▼

Code quality checks require a local repository with Bash-based execution and a start.sh workflow file. The Skill applies to repositories where code changes are staged and ready for verification.

Can I integrate these checks into CI/CD workflows?▼

Yes, the Skill's start.sh commands (check, typecheck, lint, lint-fix) are designed for integration into CI pipelines or local development to catch issues early before commits are pushed.

What happens if code quality checks fail?▼

Failed checks surface type errors, linting violations, and static analysis issues. You can then run `./start.sh lint-fix` to auto-correct fixable issues or address failures manually before rerunning checks.

Related Skills

NirusanNirusan
7

sync-config

Synchronize local Claude configuration files to a GitHub repository.

Community
Basic
UnsupervisedcomUnsupervisedcom
49

commit.commit_and_push

Commit and push validated code changes after lint passes.

Official
Basic
hopeoverturehopeoverture
6

eslint-prettier-husky-config

Configure ESLint v9, Prettier, Husky, and lint-staged for Next.js projects.

Community
Advanced
gitgoodordietryinggitgoodordietrying
1

cicd-pipeline

Automate CI/CD pipelines with GitHub Actions across Node.js, Python, Go, and Rust.

Community
Advanced