Loading...
Loading...
Found 594 Skills
Review Gitea/Forgejo pull requests — checkout, approve, reject, request reviewers, inline comments, and diff/patch/files.
You MUST use this when verified work awaits a decision on how it leaves the branch - merging it, pushing it, opening a pull request (PR), keeping the branch, discarding the branch, or cleaning up a worktree or workspace - in any repository. Not for work that is not verified yet (verify), open review findings (cr-received), a plain commit with no integration decision, or release work with its own checklist. Replaces devflow branch-finish.
Git workflow guidance for commits, branches, and pull requests
Create high-quality Pull Requests with conventional commits and proper descriptions. Trigger: When creating PRs, writing PR descriptions, or using gh CLI for pull requests.
GitHub CLI workflows for repositories, issues, pull requests, actions, releases, projects, and API calls. Use when creating PRs, reviewing code, triaging issues, triggering workflows, publishing releases, managing projects, verifying attestations, or querying the GitHub API. Use for gh cli, github automation, code review, release management.
Implements a complete workflow for resolving GitHub issues directly from Claude Code. Guides through the full lifecycle from fetching issue details, analyzing requirements, implementing the solution, verifying correctness, performing code review, committing changes, and creating a pull request. Use when user asks to "resolve issue", "implement issue", "work on issue
This skill should be used when creating conventional commits for current changes and then submitting the current branch as a pull request for code review. It combines the git:commit and git:submit-pr skills into a single workflow.
Create a PR from current commits and/or local changes. Identifies base branch, creates topic branch if needed, commits changes, and opens a PR.
Triages unresolved PR review comments using gh-pr-reviews. Analyzes code context and classifies each comment as Agree / Partially Agree / Disagree. Use when the user wants to triage, review, or analyze unresolved PR comments.
Summarize current work, commit, push, and create or update a PR. Automatically write conversation context into the PR description to ensure reviewers can quickly understand the background.
Create or update a GitHub pull request with a Japanese title and body, using .github/pull_request_template.md or docs/pull_request_template.md when present. Use when the user asks to open a PR, create a pull request, or refresh PR metadata. Requires a pushed branch—use push (and pull if needed) first; use commit-jp for commits.
Split a large PR diff into reviewable sub-patches for easier code review.