Loading...
Loading...
Found 11 Skills
GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows
Create GitHub pull requests from code changes via API or generate PR content in chat. Use when user wants to create/open/submit PR, mentions pull request/PR/merge request/code review, or asks to show/generate/display/output PR content in chat (give me PR, PR to chat, send PR to chat, etc).
Keep a Blume docs site in sync with the product it documents. Audit recently merged pull requests, changelogs, config schemas, CLI help, and public APIs against the docs content, update only pages that are factually stale, verify the docs build, and open (or update) a maintenance pull request — or report a clean no-op. Use when asked to check docs for drift, refresh stale documentation, run a scheduled docs audit, or keep docs current after a release.
Safely merge GitHub pull requests using comprehensive pre-merge validation. Use this skill when the user asks to merge a PR, complete a PR workflow, or check if a PR is ready to merge. Validates CI/CD status, reviews, and conflicts before merging with the appropriate strategy.
Create a fresh branch, complete work, and open a pull request
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.
Create GitHub pull requests with readiness checks, auto-drafted titles and descriptions, and remote push handling. Use when: create PR, pull request, open PR, submit PR, create pull request, PR for review, push and PR, pull-request, /pull-request.
End-to-end open-source contribution for Agent/LLM projects: discover GitHub repos (stars, downloads/usage, recent commits, issue close ratio, PR merge speed, release cadence) and rewrite each project description in the user's language (what it does, problem, scenarios), analyze an Agent/LLM repo, write a scoped PR plan, implement it, open a GitHub PR, then write a PR summary from saved artifacts. Use when the user wants to search for contributable projects, find open source projects, Agent open source, MCP/LangChain repositories, star 1000, GitHub repo search; pastes a GitHub URL for open source contribution analysis, PR direction, good first issue, Agent architecture flaws; asks for technical solution, implement the plan, submit PR with feat/fix/refactor/test/docs; or produce PR summary, summary.md, review submitted PR, pastes a pull request URL / previously mentioned project. Trigger even without the word skill. Do not use for private product feature work or non-Agent general OSS drive-bys.
Set up a Superset open-source contribution — fork and clone superset-sh/superset, run local dev setup, and follow the repo's contribution rules through to a merge-ready PR. Use when the user wants to contribute to Superset, fix a Superset bug themselves, or prepare a PR against superset-sh/superset.
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.