Loading...
Loading...
Found 348 Skills
Use When: Submitting code to a Git repository and generating standardized commit messages
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.
Use anime-style multi-role continuous conversational code review to output review opinions with natural technical anchors through strong character interaction
Automatically generate intelligent PR descriptions by analyzing code changes. Uses Git diffs, commit history, and context to create comprehensive pull request descriptions with summary, changes, testing notes, and breaking changes.
Refactor code with safety nets — tests green before and after, no behavior change
Commit changes and create a pull request to the official upstream repo
Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning.
Summarize authored commits over a user-specified time period into a concise update
Use git worktrees for parallel development on multiple branches simultaneously
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Generates changelogs and manages releases. Use when updating changelogs, pushing changelog changes, preparing releases, or tagging versions.
Create a Pull Request from the current branch. Syncs upstream main/master, updates current branch, handles fork remotes intelligently, and generates PR title/description from diff and commits. Respects PR templates if present. REQUIRES Must be in a git repository with gh CLI available.