check-memory-safety
Check Mojo code for memory safety issues (ownership violations, use-after-free, etc.). Use to catch memory bugs.
Découvrez les skills Outils, comparez leurs dépôts et consultez leurs instructions.
Check Mojo code for memory safety issues (ownership violations, use-after-free, etc.). Use to catch memory bugs.
Identify code quality issues and anti-patterns. Use when reviewing code for maintainability problems.
Scan code for security vulnerabilities and unsafe patterns. Use before committing sensitive code or in security reviews.
Validate and verify dependencies are available and compatible. Use when setting up environments.
Measure model performance on test datasets. Use when assessing accuracy, precision, recall, and other metrics.
Validate GitHub Actions workflow files for syntax, best practices, and correctness. Use before committing workflow changes or when workflows fail.
Create isolated git worktrees for parallel development. Use when working on multiple issues simultaneously.
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.
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é.