create-pr
Create a pull request after code changes are complete and reviewed. Use proactively after self-review passes and documentation is updated.
Découvrez les skills business git workflows, comparez leurs dépôts et consultez leurs instructions.
Create a pull request after code changes are complete and reviewed. Use proactively after self-review passes and documentation is updated.
PR review workflow after push. Use proactively immediately after creating a pull request to check CI status and Codex review results.
Protect against wrong-repo edits and enforce production parity assumptions.
Remove completed or abandoned worker worktrees and their branches. Use to clean up after workers finish their tasks.
Spawn a Claude worker to handle a GitHub issue. Fetches issue details, creates a feature branch, and works autonomously. Use when you want to delegate an issue to a worker.
Spawn a Claude worker to handle a GitHub issue. Fetches issue details, creates a feature branch, and works autonomously. Use when you want to delegate an issue to a worker.
List all active Claude workers and their git worktrees. Shows branch status, commits, and suggests next actions. Use to see what workers are running.
Guide git operations using a three-tier branching model (main → staging → feature). Use this skill when the user asks about git commands, branch strategy, PRs, rebasing, merging, deploying to production, hotfix...
Gitea operations via tea CLI. Use when user mentions: gitea, tea, or when git remote shows a Gitea instance.
GitLab operations via glab CLI. Use when user mentions: MR, merge request, gitlab issue, pipeline, CI status, glab, or when git remote shows gitlab.com or self-hosted GitLab.
GitHub operations via gh CLI. Use when user mentions: PR, pull request, github issue, workflow, actions, gh, or when git remote shows github.com.
Use after completing and verifying a task. Checks git branch (feature → suggests finishing-a-development-branch), closes task, recursively checks parents with confirmation, runs bd sync. Handles task completion...
Stage, commit, and push changes to the current branch. Use when asked to commit changes, push code, or after completing a task.
Create a pull request for the current branch using GitHub CLI. Use after committing changes when ready to open a PR.
Guide feature-based directory structure and file placement. Apply when creating new files or organizing code. Enforce naming conventions and import ordering for backend and frontend files.
Enforce 500-line file size limits. Warn at 400 lines. Guide splitting large files into focused modules. Apply when writing or editing code.
Proactively remind about Gabe-OS workflows when context may have been lost, especially after /compact operations. Prevent manual implementation by checking for existing specs first.
Generates a journal entry from git commit history - just say "journal this" and I'll read the commits and write it up
Git-backed issue tracker for multi-session work with dependencies and persistent memory across conversation compaction. Use when work spans sessions, has blockers, or needs context recovery after compaction. Tr...
Generates PR descriptions, commit messages, release notes, and manages branch strategies, changelog automation, and git hooks. Use when creating pull requests, writing commits, preparing releases, managing bran...
Audit codebase stability guardrails - tests, ESLint, pre-commit hooks, CI/CD, dead code detection with Knip. Finds unused files, exports, and dependencies. Use /codebase-stability-audit:run to start.
Professional codebase setup for developers migrating from Lovable, Bolt, or v0. Provides feature-based architecture scaffolding, naming convention checks, and config-driven pattern migration.
Analisa commits e sugere testes necessários (unit, integration, contract, smoke, E2E). Roda em background após commits.
aytordev directory structure and module placement. Guide for understanding the modules directory structure and placement in aytordev's system.
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é.