Loading...
Loading...
Found 422 Skills
Analyzes git diff and commit history to write PR title and description based on the project's PR template.
Split changes into a Graphite stack with PR titles and descriptions. Use when asked to create or propose a stacked PR series.
Assists in creating, modifying, viewing or managing GitHub Pull Request (PR). Automatically analyzes branch commits and change content, generates compliant Traditional Chinese PR titles and descriptions. Use cases include: (1) Create a new PR from the current branch, (2) Modify the title, description, reviewers or labels of an existing PR, (3) Check the PR status of the branch (open, merged, closed), (4) Need to automatically aggregate multiple changes to generate a summary. Applicable to scenarios with requests such as "create PR", "create pull request", "help me open a PR", "modify PR content". Operations are executed via GitHub CLI (gh).
Create a git branch following Sentry naming conventions. Use when asked to "create a branch", "new branch", "start a branch", "make a branch", "switch to a new branch", or when starting new work on the default branch.
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
Configure GitHub authentication for Cyrus — gh CLI login and git config for creating pull requests.
Commit unstaged changes, push changes, submit a pull request.
Chinese Git Commit Specification - Commit Message Standards and Changelog Automation Adapted for Domestic Teams
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.
Generate high-quality Conventional Commit messages for repositories using conventional-changelog-conventionalcommits.
Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
Write a description to description GitHub Pull Request.