auto-doc
Automatic codebase documentation maintenance system. Use this skill ALWAYS when making ANY code changes including creating, modifying, deleting, or moving files. Enforces three-tier documentation (root ARCHITEC...
Discover blockchain git workflows skills, compare source repositories and read the instructions for each workflow.
Automatic codebase documentation maintenance system. Use this skill ALWAYS when making ANY code changes including creating, modifying, deleting, or moving files. Enforces three-tier documentation (root ARCHITEC...
Split staged changes into a sequence of Conventional Commits (reusing repo commit types/scopes), then push and create a GitHub PR via `gh` using the repo’s PR template.
Help address CodeRabbit AI and ChatGPT Codex Connector comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
Reviews code changes for complexity and simplification opportunities. Use before creating PRs or when reviewing changesets.
Reviews test coverage and testing strategy for recent code changes. Use before creating PRs to ensure changes are well-tested.
AI-powered coding assistant providing inline suggestions, chat interface, code review, and autonomous coding agent across IDEs and GitHub.com
LobeHub CLI Toolbox - AI-powered command-line tools including lobe-commit (ChatGPT Git commits with Gitmoji), lobe-i18n (automated internationalization), and lobe-label (GitHub label management)
GitBook documentation platform - creating docs, publishing sites, Git sync, API references, and collaboration
Automate versioned releases of NPM packages to GitHub repositories. Use this skill when setting up or configuring release-it for version bumping, changelog generation, npm publishing, GitHub releases, and CI/CD...
Crée une Pull Request en mode Continuous Delivery avec workflow complet : QA, labels version (major/minor/patch), feature flags, code review automatique.
Skill interne fournissant les scripts communs pour la création de Pull Requests. Ne pas appeler directement - utilisé par git-pr et git-cd-pr.
Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
Use for QUICK PR reviews with structured checklists (architecture, patterns, security, performance). Provides step-by-step review process, git diff commands, and review report templates. Best for pull request r...
Stage changes and create git commits with conventional commit messages. Use when asked to "commit", "stage and commit", "save changes", or after completing implementation tasks. Alias for /git/cm.
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success c...
Use for QUICK PR reviews with structured checklists (architecture, patterns, security, performance). Provides step-by-step review process, git diff commands, and review report templates. Best for pull request r...
Use when reviewing code changes, pull requests, or performing refactoring analysis with focus on patterns, security, and performance.
Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
Use when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
Use when the user asks to compare branches, analyze git diffs, review changes between branches, update specifications based on code changes, or analyze what changed. Triggers on keywords like "compare branches"...
Review and merge open PRs for GitHub issues as a cohesive batch
Review and merge open PRs for claimed ba tasks as a cohesive batch
Work a ba task to completion in a branch, including review follow-ups, then PR for human review
Address PR comments for GitHub issue PRs, resolve feedback, push fixes
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.