Loading...
Loading...
Found 132 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.
Analyze failed GitHub Action jobs for a pull request.
Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.
Lead Software Engineer. Use this skill whenever the user mentions coding, debugging, refactoring, or implementation, even if they don't explicitly ask for an "engineer." Use it to translate technical blueprints into clean code.
GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.
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.
Format git commit messages and Pull Request titles using Conventional Commits with a deterministic gitmoji prefix. Use when generating or suggesting commit messages, PR titles, or when the user says "commit this", "create PR", "write a commit", "prepare PR", or similar.
GitHub PR lifecycle: branch, commit, open, CI, merge.
Git branch completion workflow. Use when implementation is complete, tests pass, and a feature branch needs to be integrated via merge, pull request, or cleanup.
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
Review a GitHub pull request using Alan's GitHub MCP tools
Provides automated, context-aware code reviews focusing on logic errors and style violations. Use during Pull Request cycles to identify potential bugs and maintain high code quality standards.