Tools & Utilities
Essential command-line tools and system utilities.
workflow-management
Manage GitHub Actions workflows - trigger, monitor, view logs, and download artifacts using gh CLI
security-github-review
Security review workflow for GitHub repositories using the Security MCP (OWASP ASVS + NIST 800-53) as the primary reference and mapping layer. Use when asked to security review a repo, produce an OWASP/NIST-aligned checklist, map findings to ASVS/NIST controls, generate a prioritized vulnerability report, or create security requirements/acceptance criteria from repo code/config.
code-review
Comprehensive code review and health check. Use when user needs project audit, code quality check, conflict detection, or says "review code", "check project", "audit codebase", "health check", "find issues", "code quality".
code-review
Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
analyze-code
Intelligence-first code analysis for bugs, architecture, performance, and security. Use proactively when investigating code issues, tracing dependencies, or understanding system behavior. MUST query project-intel.mjs before reading files.
installation-token-generation
Generate short-lived installation tokens from GitHub App credentials with actions/create-github-app-token. Organization-scoped and repository-scoped patterns for automated cross-repo workflows.
dev-test-playwright
Playwright MCP browser testing. Headless E2E, cross-browser, CI/CD automation.
git-committer
Analyze staged changes and create meaningful git commits with appropriate commit messages following conventional commit standards. Automatically groups changes into logical units and presents multiple commit options (single vs. multiple commits) before execution. Always waits for user confirmation.
dx-maintainability-reviewer
Evaluate how easy it is for new engineers to work in a codebase. Use when assessing code quality, onboarding friction, or technical debt. Triggers on "code quality", "maintainability", "developer experience", "DX review", "onboarding", "cognitive load", "code smell", "refactoring", "tech debt".
git-workflow-management
Automate frequent Git operations including adding changes, committing with meaningful messages, and pushing to remote repositories. Use when you need to save progress, commit code changes, or maintain regular version control workflow with proper commit practices.
creating-branches
Git Flow branch creation workflow with worktree support. Creates feature/, release/, hotfix/ branches with automatic worktree setup. Use when creating branches for new work items.
smith-tools
Tool configurations for IDEs, MCP integrations, and development tools. Use when configuring IDE settings, MCP tools, or pytest. Covers conditional tool activation, configuration hierarchy, and synchronization patterns.
flow-next-impl-review
John Carmack-level implementation review via RepoPrompt or Codex. Use when reviewing code changes, PRs, or implementations. Triggers on /flow-next:impl-review.
testing-practices
Testing best practices for modern Python development. Activated when working with tests, pytest, Hypothesis property-based testing, Atheris fuzz testing, test coverage, test organization, or mutation testing.
git-expert
Use when working with git operations including commits, branches, worktrees, PRs, and Graphite stacked PRs. Covers the full git workflow from feature isolation to PR submission.
github-actions-reusable-workflows-expert
Expert guidance for creating and maintaining GitHub Actions workflows and reusable workflows with security best practices
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
testing-standards
This skill should be used when the user asks about "testing", "test coverage", "unit tests", "integration tests", "test organization", "test best practices", "flaky tests", "test isolation", "TDD", "regression tests", or needs guidance on test structure, coverage requirements, and test execution.
test-coverage
This skill should be used when the user asks to "analyze test coverage", "find untested code", "check coverage gaps", "improve test coverage", "identify missing tests", "measure code coverage", "test quality analysis", or mentions testing strategies and coverage metrics.
secrets-management
Secure storage, rotation, and access control for secrets, credentials, and sensitive configuration.
