code-quality

From gemini-pair-pipeline

Description

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

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 13 hours ago

Related Skills

Skill Development

46.4K

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

From plugin-dev

Agent Development

46.4K

This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.

From plugin-dev

Command Development

46.4K

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.

From plugin-dev