GitHub
codebase-map
Generate a structural overview and dependency diagram of the codebase. Use when the user wants to understand codebase structure, visualise architecture, or says "/codebase-map".
Skills IA databases automation tools
Découvrez les skills databases automation tools, comparez leurs dépôts et consultez leurs instructions.
Catégories: databases automation tools
databases automation tools Effacer les filtres
Explorer
GitHub
review-pr
Review a pull request using Google's code review principles. Takes a PR number or auto-detects from current branch. Use when the user wants to review a PR, check PR changes, or says "/review-pr 123".
GitHub
coderabbit-request
Use after completing file changes - strongest for source code (AST-aware linting, security, tests), lighter support for markdown/config. Dispatches CodeRabbit reviewer subagent. ALWAYS request review before con...
GitHub
review-optimization
Reviews memory optimization patches using a 5-persona peer review system. Requires unanimous approval backed by benchmarks. Bugs discovered during review are valuable - invoke /validate-correctness to validate...
GitHub
pre-pr
Review code changes against spec for drift and principle violations before PR submission. Use when user says "pre-pr review", "check against spec", "review my changes", "spec drift", "am I following the spec",...
GitHub
component-docs
Guide for documenting project components and features. Creates or updates documentation in docs/components/ by exploring git changes to understand implementation details. Provides templates and conventions for...
GitHub
minimal-file-changes
Prefer small, local edits. Avoid creating new files or folders unless required by Laravel conventions or explicitly requested by the user.
GitHub
pull-request-format
Validate pull request source/target rules and draft standardised PR titles and Markdown descriptions that match repository GitHub Actions enforcement.
GitHub
tests-and-formatting-discipline
Maintain testing and formatting discipline aligned with the repository CI pipeline without automatically running tools.
GitHub
project-intake
Build a fast, accurate mental model of the eo-processor repo and the user’s task. Use when starting work, when requirements are unclear, or before making multi-file changes (Rust+PyO3+Python packaging/tests/doc...
GitHub
git-commit-helper
Generate descriptive commit messages by analyzing git diffs. Use when the user asks for help writing commit messages or reviewing staged changes.
GitHub
post-bug-reflection
Self-improvement workflow after fixing any bug. Analyzes root causes and updates project guidance (CLAUDE.md, skills, commands) to prevent similar bugs. MUST be invoked after completing any bug fix before marki...
GitHub
pre-commit-check
Pre-commit validation checklist before staging and committing code. Use BEFORE every git commit to ensure code quality, tests pass, and documentation is updated. Triggers on "commit", "stage changes", "ready to...
GitHub
code-review-patterns
This skill should be used when the user asks about "code review best practices", "how to review code", "review methodology", "code review framework", "impact prioritization", "root cause analysis", or needs gui...
GitHub
root
Manage and guide Hikaze-Model-Manager-2 Codex project work via the .codex governance system. Use when the user says "root skill" or asks to start development based on the root skill, or when asked to set up or...
GitHub
release
Analyze changes, determine semantic version bump, build executables, and cut a GitHub release with Claude-written minimalist notes.
GitHub
repo-sweep
Comprehensive pre-production repository audit for preparing repos for public release. Use when the user wants to perform a "final sweep", "production check", "pre-release audit", or prepare a repository to be m...
GitHub
issue-creator
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
GitHub
issue-creator
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
GitHub
code-quality-analyst
Analyzes code changes for quality issues, code smells, SOLID violations, LLM-generated code problems, and refactoring opportunities. Reports findings with severity, evidence, and suggested fixes.
GitHub
refactor-critic
Reviews code quality analyst findings. Validates issues are real, severity is appropriate, and suggested refactorings are practical.
GitHub
issue-creator
Generate GitHub issues from an approved engineering specification. Use to break down a spec into implementable, atomic tasks with dependencies, sizing, and labels.
GitHub
refactor-moderator
Synthesizes analyst findings with critic feedback. Produces final recommendations and generates TDD-compatible refactor plans for approved issues.
GitHub
ubs-scanner
Bug scanning with UBS (Ultimate Bug Scanner). Use before commits, when scanning for bugs, when the user mentions "ubs", "bugs", "scan", or "code quality".
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é.