code-quality

From repoprompt-swarm

Description

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

Tool Access

4 tools

Limited to specific tools

Supporting Files

0 files

Additional assets for this skill

Tool Access

This skill is limited to using the following tools:

BashReadGrepGlob

Skill Content

name: code-quality description: Run code quality checks. Use after making code changes, before commits, or when asked to check code quality. allowed-tools: Bash, Read, Grep, Glob

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 1 day ago

Related Skills

Writing Hookify Rules

46.0K

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.

From hookify

frontend-design

46.0K

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.

From frontend-design

claude-opus-4-5-migration

46.0K

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.

From claude-opus-4-5-migration