code-quality

Description

Run code quality checks. Use after making code changes, before commits, or when asked to check code quality.

AI Summary

Runs type checking and linting to verify code quality after changes. Use before commits or when requested to catch errors and style issues early.

Install

Add the repository(one-time)

/plugin marketplace add GantisStorm/claude-code-pair-planning-framework

Install the plugin

/plugin install gemini-swarm@claude-code-repoprompt-codex-plugins

Tool Access

This skill is limited to using the following tools:

BashReadGrepGlob

Skill Content

Code Quality Checks

Run code quality checks after making code changes.

Commands

# Full check (type checking + linting)
./start.sh check

# Type checking only
./start.sh typecheck

# Linting only
./start.sh lint

# Linting with auto-fix
./start.sh lint-fix

Workflow

Make code changes
Run ./start.sh check
If lint errors can be auto-fixed, run ./start.sh lint-fix
Fix remaining errors manually
Re-run check to verify

Links

GitHub Stats

0 forks

Updated 22 days ago

Similar Skills

claude-opus-4-5-migration

2 files

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string updates and prompt adjustments for known Opus 4.5 behavioral differences. Does NOT migrate Haiku 4.5.

claude-opus-4-5-migration

53.4k

Writing Hookify Rules

This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs guidance on hookify rule syntax and patterns.

hookify

53.4k

frontend-design

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

frontend-design

53.4k