Loading...
Loading...
Found 225 Skills
Use when writing, generating, or drafting a pull request description. Always use this skill when the user asks to "write a PR description", "create a PR", "draft a pull request", "generate PR text", or similar. Produces a complete, structured PR description following the team's conventions: ticket-key title, Purpose, Approach with implementation details, and a Pre-Review Checklist.
Use when reviewing code, pull requests, branches, diffs, or changed files for quality, correctness, security, performance, and style issues.
Create GitHub Pull Request from specification using pull_request_template.md. Use when: spec needs to be converted to PR, spec is ready for review/merge, need to automate PR creation from specification file with template-based body and title.
Open a pull request for the current feature
Git workflow guidance for commits, branches, and pull requests
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an
Reviews code changes for correctness, maintainability, security, and adherence to project conventions. Use when reviewing PRs, auditing recent changes, or getting a second opinion on implementation quality.
Analyze failed GitHub Action jobs for a pull request.
Perform security-focused review of code diffs and pull requests, identifying newly introduced vulnerabilities, security regressions, and unsafe patterns in changed code.
Generate a pull request description from branch changes. Use when creating a PR or preparing PR documentation.
Create a PR from current commits and/or local changes. Identifies base branch, creates topic branch if needed, commits changes, and opens a PR.
Land a PR by monitoring conflicts, resolving them, waiting for checks, and squash-merging when green; use when asked to land, merge, or shepherd a PR to completion.