doc-update-blog
Update development blog with implementation milestones, learnings, and progress. Use after completing major milestones or phases.
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.
Update development blog with implementation milestones, learnings, and progress. Use after completing major milestones or phases.
Generate test coverage reports showing which code paths are tested. Use to identify untested code and improve test coverage.
Validate agent YAML frontmatter and configuration. Use before committing agent changes or in CI.
Format Mojo code using mojo format command. Use when preparing code for commit or when formatting checks fail.
Refactor and finalize code after parallel phases complete, addressing technical debt. Use in cleanup phase to polish code before merge.
Create changelog from git commits. Use when preparing release notes.
Comprehensively review a pull request including code changes, CI status, and adherence to project standards. Use when asked to review a PR.
Verify memory safety in Mojo code including ownership, borrowing, and lifetime management. Use when reviewing code or debugging memory issues.
Validate Mojo code patterns (out self, mut, List, etc.) against best practices. Use to ensure code follows project standards.
Build Mojo packages (.mojopkg files) for distribution. Use when creating distributable libraries or during packaging phase.
Post structured updates to GitHub issues. Use to report progress, findings, and implementation notes directly to issues.
Analyze code complexity metrics including cyclomatic complexity and nesting depth. Use to identify code that needs refactoring.
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.
Run local builds with proper environment setup. Use when building code locally to verify changes before pushing.
Generate Architecture Decision Records (ADRs) to document significant architectural decisions. Use when making important technical decisions that need documentation.
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.
Generate comprehensive plan documentation following Template 1 format. Use when creating plan.md files for new components or subsections.
Create starter code from templates. Use when setting up new modules or test files.
Examine code organization and identify structural patterns. Use when reviewing module design.
Check CI/CD status of a pull request including workflow runs and test results. Use when verifying if PR checks are passing or investigating CI failures.
Address PR review feedback by making changes and replying to comments. Use when a PR has open review comments needing responses.
Review PR changes with structured checklist for quality and standards compliance. Use for comprehensive PR code review.
Check agent configuration coverage across hierarchy levels and phases. Use to ensure complete agent system coverage.
Run all configured linters including mojo format, markdownlint, and pre-commit hooks. Use before committing code to ensure quality standards are met.
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.