refactor-code
Restructure code for improved clarity and maintainability. Use when addressing code smells or technical debt.
Browse published AI skills maintained by mvillmow. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
85Repository stars across indexed skills
1,105Repository forks
340Average repository stars per indexed skill
13Repository stars may repeat across skills from the same repository.
Restructure code for improved clarity and maintainability. Use when addressing code smells or technical debt.
Generate review checklists for different change types. Use to customize review focus based on what was changed.
Batch merge multiple PRs by label (e.g., all 'ready-to-merge' PRs). Use when you have multiple approved PRs to merge.
Create GitHub Actions workflows for automated package building and distribution. Use in package phase to automate .mojopkg building and release creation.
Read context from GitHub issue including body and comments. Use before starting implementation work or when prior context is needed.
Analyze test differences between runs to identify flaky tests and consistency issues. Use to find tests that fail intermittently.
Run pre-commit hooks locally or in CI to validate code quality before committing. Use to ensure commits meet quality standards and CI will pass.
Measure execution time and memory usage of code. Use when analyzing performance characteristics.
Apply SIMD optimizations to Mojo code for parallel computation. Use when optimizing performance-critical tensor and array operations.
Remove merged or stale git worktrees. Use after PRs are merged, work is done, or when worktrees are no longer needed.
Create test cases for functions and modules. Use when implementing TDD or improving coverage.
DEPRECATED: The notes/plan/ directory has been removed. Planning is now done directly through GitHub issues. See gh-read-issue-context and gh-post-issue-update skills instead.
Parse and interpret mathematical equations from research papers. Use when extracting formulas for implementation.
Switch between git worktrees for parallel development. Use when working on multiple issues simultaneously.
Create docstrings for functions and classes. Use when documenting code APIs.
Track implementation progress against plan. Use to monitor component delivery and identify blockers.
Test agent delegation patterns to verify hierarchy and escalation paths. Use after modifying agent structure.
Sync git worktrees with remote and main branch changes. Use to keep long-running feature branches up-to-date.
Validate type safety in Mojo code including parametric types and trait constraints. Use during code review or when type errors occur.
Detect security vulnerabilities in code and dependencies. Use when auditing security.
Extract and summarize test failures from logs. Use to quickly understand what tests failed and why.
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
Generate test files and coordinate test-driven development (TDD). Use when creating tests before implementation or during test phase.
Create a pull request properly linked to a GitHub issue using gh pr create --issue. Use when creating a PR that implements or addresses a specific issue.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.