worktree-sync
Sync git worktrees with remote and main branch changes. Use to keep long-running feature branches up-to-date.
Découvrez les skills Outils, comparez leurs dépôts et consultez leurs instructions.
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.
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.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.