plan-create-component
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.
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
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.
Validate markdown files for formatting, links, and style compliance using markdownlint. Use before committing documentation changes.
Reply to PR review comments using the correct GitHub API endpoint. Use when responding to inline code review feedback (not gh pr comment).
Analyze imports and identify all module dependencies. Use when mapping project structure.
Parse and analyze CI failure logs to identify root causes and error patterns. Use when CI builds fail to understand what broke.
Parse and document algorithm pseudocode from research papers. Use when preparing for implementation.
Post structured documentation to GitHub issue as a comment. Use when starting work on an issue to document approach and track progress.
Check function inputs for correctness and safety. Use when implementing defensive programming.
Check code for style and quality issues. Use when validating code before commits.
Create distributable packages including .mojopkg files and archives. Use during package phase to prepare components for distribution.
Execute test suites and report results. Use when validating code functionality.
Run Mojo tests using mojo test command. Use when executing tests or verifying test coverage.
Automatically fix code formatting issues using mojo format, markdownlint, and pre-commit hooks. Use when formatting checks fail or before committing code.
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.