worktree-merge
Use when merging parallel worktrees back together after parallel implementation
Use when merging parallel worktrees back together after parallel implementation
Update the status of a GitHub Issue to any available status in all linked projects using the `gh project item-edit` command. Allows interactive status selection via CLI.
Clean and normalize a large backlog of GitHub pull requests in messy repositories. This skill should be used when facing a repository with numerous stale, conflicted, or outdated PRs that need systematic review, conflict resolution, testing, and disposition (merge, close, or defer). Handles PR triage, automated rebasing, CI verification, risk assessment, and safe merging while maintaining default branch stability.
Stages all changes and generates clear commit messages following conventional commit format. Use when ready to commit your work.
Create a GitLab merge request using glab CLI with the first commit message as the title
Use this skill when working with Graphite (gt) for stacked PRs, when the user mentions pull requests, Graphite, stacking, or gt commands. Ensures proper use of gt commands instead of raw git for stack-aware operations.
Use when encountering merge conflicts - handle conflicts cleanly, verify resolution, and maintain code integrity
Detect GitHub repository name and owner from git remotes. Use when needing repo identifier for GitHub CLI, API calls, or when working with multiple repositories. Automatically extracts owner/repo format.
Automatically discover, score, and archive relevant GitHub repositories for BidDeed.AI and Life OS projects. Use this skill when the user requests to find GitHub repositories for specific topics, technologies, or domains that could be integrated into existing projects. Triggers include phrases like "find GitHub repos for", "discover repositories about", "search GitHub for projects related to", or when analyzing videos/articles that mention GitHub projects.
Create atomic Git commits with proper messages and co-author signatures. Use when the user asks to "commit my changes", "make a commit", "save my work", or mentions committing code changes. Focuses on commit message formatting, atomic commits, and maintaining consistent co-authorship attribution.
Upsert a single PR comment that serves as an AI session ledger (human steering, deltas, tests) across Codex + Claude Code. Not a PR description.
Initializes and clones Git repos. Use for setup/new projects. Triggers - start repo, clone from remote.
Start a PR review inline comments fixing session. Use when users want to address, fix, or resolve inline review comments on a GitHub PR. Fetches unresolved comments and helps fix each one systematically.
Use Git worktrees to isolate tasks and keep diffs small and parallelizable
Git branch cleanup utility. Lists and deletes branches that have been merged to main. Use when user wants to clean up old branches, delete merged branches, or tidy up their git repository.
Create a GitHub issue. Use when the user wants to create an issue, open an issue, or report a bug/feature request.
MUST use when working with spec files in `specs/` directories, or when commands reference this skill for conventions.
Create or switch to feature branches with proper naming conventions. Use when user wants to start working on a new feature, start a feature. Generates feature/branch-name patterns from descriptions, checks existence, and creates/switches accordingly.
Guides contributors through adding new skills to the claude-code-skills repository via Pull Request with proper validation and documentation
Creates a sub-issue linked to a parent GitHub issue. Use when: user wants to create a sub-issue, break down an issue, or add child task.