Essential command-line tools and system utilities.
Help with Git operations for this dotfiles repository, including creating contextual commit messages, reviewing changes, and following best practices for dotfiles version control. Use when the user wants to commit changes, review diffs, create branches, or perform git operations specific to dotfiles management.
Reply to PR review comments using the correct GitHub API endpoint. Use when responding to inline code review feedback (not gh pr comment).
Provide safe git commands for common tasks. Use when a junior developer needs help with branching, commits, or resolving simple conflicts.
Provides formatting guidelines for prose. This skill's guidance is automatically applied when writing multi-line comments, commit messages, markdown, or other prose.
Generate fix suggestions based on error patterns and best practices. Use when analyzing failures to get actionable remediation steps.
Reference guide for code comment formatting rules and examples. The core rules are automatically applied via CLAUDE.md system instructions - this skill provides detailed examples and edge cases for reference.
Automatically fix code formatting issues using mojo format, markdownlint, and pre-commit hooks. Use when formatting checks fail or before committing code.
Run code quality linters when reviewing code. Checks style, complexity, and best practices. Supports Python (ruff), JavaScript (eslint), Go (golangci-lint), Ruby (rubocop), Java (Checkstyle/PMD). Use when reviewing any code changes for quality issues.
Generate comprehensive test coverage reports when reviewing code. Identifies untested code paths and low-coverage areas. Supports Python (pytest-cov), JavaScript (jest), Go (go test -cover), Java (JaCoCo). Use when reviewing tests or before approving code changes.
The model must invoke this skill when any trigger occurs - (1) user mentions "clang-format" or ".clang-format", (2) user requests analyzing code style/formatting patterns/conventions, (3) user requests creating/modifying/generating formatting configuration, (4) user troubleshoots formatting behavior or unexpected results, (5) user asks about brace styles/indentation/spacing/alignment/line breaking/pointer alignment, (6) user wants to preserve existing style/minimize whitespace changes/reduce formatting diffs/codify dominant conventions.
Identify code quality issues and anti-patterns. Use when reviewing code for maintainability problems.
Comprehensive markdown linting guidance using markdownlint-cli2. Run, execute, check, and validate markdown files. Fix linting errors (MD0XX rules). Configure .markdownlint-cli2.jsonc (rules and ignores). Set up VS Code extension and GitHub Actions workflows. Supports markdown flavors including GitHub Flavored Markdown (GFM) and CommonMark. Use when working with markdown files, encountering validation errors, configuring markdownlint, setting up linting workflows, troubleshooting linting issues, establishing markdown quality standards, or configuring flavor-specific rules for tables, task lists, and strikethrough.
This skill should be used when the model needs to ensure code quality through comprehensive linting and formatting. It provides automatic linting workflows for orchestrators (format → lint → resolve via concurrent agents) and sub-agents (lint touched files before task completion). Prevents claiming "production ready" code without verification. Includes linting rules knowledge base for ruff, mypy, and bandit, plus the linting-root-cause-resolver agent for systematic issue resolution.
Generate test coverage reports showing which code paths are tested. Use to identify untested code and improve test coverage.
Analyze imports and identify all module dependencies. Use when mapping project structure.
Refactor and finalize code after parallel phases complete, addressing technical debt. Use in cleanup phase to polish code before merge.
Create complete runnable companion projects for articles - scaffolded projects, not snippets
When reading or writing pyproject.toml or .toml config files in Python. When editing TOML while preserving comments and formatting. When designing configuration file format for a Python tool. When code uses tomlkit or tomllib. When implementing atomic config file updates.
Create starter code from templates. Use when setting up new modules or test files.
Restructure code for improved clarity and maintainability. Use when addressing code smells or technical debt.
Create a changeset file for versioning and changelog generation. Use when the user asks to add a changeset, bump version, or prepare a release.
Analyzes codebase to find similar features, reusable utilities, and architectural patterns
Open source license compliance including compatibility analysis, obligations tracking, and compliance workflows
Safe refactoring workflow for replacing old types with new type-safe implementations through integration-test-first, file-by-file migration with incremental verification
