GitHub
analyze-equations
Parse and interpret mathematical equations from research papers. Use when extracting formulas for implementation.
☆ 13View skill
DevOps AI Skills
Discover DevOps skills, compare source repositories and read the instructions for each workflow.
Categories: DevOps
DevOps Clear filters
Browse skills
GitHub
worktree-switch
Switch between git worktrees for parallel development. Use when working on multiple issues simultaneously.
☆ 13View skill
GitHub
generate-docstrings
Create docstrings for functions and classes. Use when documenting code APIs.
☆ 13View skill
GitHub
track-implementation-progress
Track implementation progress against plan. Use to monitor component delivery and identify blockers.
☆ 13View skill
GitHub
agent-test-delegation
Test agent delegation patterns to verify hierarchy and escalation paths. Use after modifying agent structure.
☆ 13View skill
GitHub
worktree-sync
Sync git worktrees with remote and main branch changes. Use to keep long-running feature branches up-to-date.
☆ 13View skill
GitHub
mojo-type-safety
Validate type safety in Mojo code including parametric types and trait constraints. Use during code review or when type errors occur.
☆ 13View skill
GitHub
scan-vulnerabilities
Detect security vulnerabilities in code and dependencies. Use when auditing security.
☆ 13View skill
GitHub
extract-test-failures
Extract and summarize test failures from logs. Use to quickly understand what tests failed and why.
☆ 13View skill
GitHub
agent-hierarchy-diagram
Generate visual hierarchy diagrams of agent system showing levels and delegation. Use for documentation or onboarding.
☆ 13View skill
GitHub
phase-test-tdd
Generate test files and coordinate test-driven development (TDD). Use when creating tests before implementation or during test phase.
☆ 13View skill
GitHub
gh-create-pr-linked
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.
☆ 13View skill
GitHub
doc-update-blog
Update development blog with implementation milestones, learnings, and progress. Use after completing major milestones or phases.
☆ 13View skill
GitHub
quality-coverage-report
Generate test coverage reports showing which code paths are tested. Use to identify untested code and improve test coverage.
☆ 13View skill
GitHub
agent-validate-config
Validate agent YAML frontmatter and configuration. Use before committing agent changes or in CI.
☆ 13View skill
GitHub
mojo-format
Format Mojo code using mojo format command. Use when preparing code for commit or when formatting checks fail.
☆ 13View skill
GitHub
phase-cleanup
Refactor and finalize code after parallel phases complete, addressing technical debt. Use in cleanup phase to polish code before merge.
☆ 13View skill
GitHub
generate-changelog
Create changelog from git commits. Use when preparing release notes.
☆ 13View skill
GitHub
gh-review-pr
Comprehensively review a pull request including code changes, CI status, and adherence to project standards. Use when asked to review a PR.
☆ 13View skill
GitHub
mojo-memory-check
Verify memory safety in Mojo code including ownership, borrowing, and lifetime management. Use when reviewing code or debugging memory issues.
☆ 13View skill
GitHub
validate-mojo-patterns
Validate Mojo code patterns (out self, mut, List, etc.) against best practices. Use to ensure code follows project standards.
☆ 13View skill
GitHub
mojo-build-package
Build Mojo packages (.mojopkg files) for distribution. Use when creating distributable libraries or during packaging phase.
☆ 13View skill
GitHub
gh-post-issue-update
Post structured updates to GitHub issues. Use to report progress, findings, and implementation notes directly to issues.
☆ 13View skill
GitHub
quality-complexity-check
Analyze code complexity metrics including cyclomatic complexity and nesting depth. Use to identify code that needs refactoring.
☆ 13View skill
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.