finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Discover tools git workflows skills, compare source repositories and read the instructions for each workflow.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream rep...
Detect and configure quality gate commands for Ralph's autonomous execution. Use when: (1) Analyzing a project to determine available test, lint, and build scripts, (2) Generatiing a task-specific verification...
Use GitHub CLI (gh) to interact with GitHub repositories, pull requests, issues, and workflows. Use when: (1) Reading PR details, diffs, or metadata, (2) Listing or filtering PRs and issues, (3) Creating PR com...
"Work with git worktrees and workspaces for concurrent development. Use when: (1) Creating new workspaces with \`git worktree add\`, (2) Listing existing worktrees with \`git worktree list\`, (3) Removing workt...
Review pull requests by integrating GitHub operations with Linear issue tracking. Use when: (1) Validating PR changes against Linear issue requirements, (2) Checking if PR addresses all acceptance criteria from...
Post-checkout git hook for automatic worktree setup. Use when: (1) Setting up automatic configuration for new git worktrees, (2) Creating post-checkout hooks that detect new worktrees and run setup tasks, (3) C...
Generate professional release notes from git commits between two refs with automated categorization. Use when creating release notes from git history.
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 when updating specifications, comparing branches, or ensuring documentation reflects current implementation.
Issue linking and dependency management - create links, view blockers, analyze dependencies, clone issues. Use when linking issues, finding blocker chains, or cloning with relationships.
Developer workflow integration for JIRA - Git branch names, commit parsing, PR descriptions. Use when generating branch names from issues, linking commits, or creating PR descriptions. Also use to troubleshoot...
Analyzes codebases to map architecture, dependencies, complexity metrics, and data flows for rapid onboarding. Use when exploring new repos, understanding project layout, analyzing dependencies, measuring code...
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...
Token-efficient git operations with security scanning and auto-split commits
Present the status of the git repository to the user. Use to display the status of the repository after a successful git commit by the agent. The agent should not use this internally for its own needs.
Iteratively, commit atomic changes to the respository. Use when the user or agent needs to autonomously commit atomic changes to the repository. Employs the "git-add", "git-message", and "git-status" in skills...
Generate a commit message for changes already in the Git staging area, and await approval from the user. Use when the agent needs to generate a commit message for staged changes. Only generates the commit messa...
Autonomously select files to stage for an atomic Git commit. Use when the agent wants to stage selected files for a git commit. Only stages selected files, but does not commit them.
Creates well-formatted git commits using Conventional Commits specification. Use when committing changes, creating commits, staging and committing files, or when asked to save work with a proper commit message.
Master Bun runtime workflows for full-stack development. Monorepos, bunx, lockfiles, performance optimization, and integration patterns.
Git history exploration and repository analysis. Use when users ask about git history ("what changed", "when did we add"), want to understand past changes, need to search commits, ask about branches, or want to...
Code review workflow using GitHub CLI. Use when reviewing pull requests, checking PR diffs, adding review comments, or approving/requesting changes on PRs.
Investigate why code was written a certain way. Use when tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes.
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.