Loading...
Loading...
Found 594 Skills
Comprehensive pull request review using specialized agents
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
Use when reviewing code, pull requests, branches, diffs, or changed files for quality, correctness, security, performance, and style issues.
Review one or all open pull requests in saadeghi/daisyui using the GitHub MCP server and isolated base-versus-PR verification. Use when Codex must fact-check a daisyUI PR, verify that it solves its stated problem or linked issue, test concrete regression risks, explain developer experience before and after, decide whether it is safe to merge, and write a concise report under tmp/pr/. Base every report statement on linked sources, inspected code, or observed command output; never invent claims, risks, results, or confidence deductions.
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this". Also activate when reviewing a pull request or diff.
GitHub operations via gh CLI and GitHub API: create/view/merge PRs, manage issues, query API endpoints, handle workflows in enterprise or public GitHub environments.
Catalyst's GitHub: show a ticket's pull request with its checks, reviews and review threads, say whether it is mergeable under this repository's policy, and explain what a PR accumulates as the ticket moves (the branch, the draft, the rewrite, the force-pushes, the labels, the queue). Use when someone asks "show me the PR", "what are the checks saying", "why hasn't it merged", "what does the queue need", "what does that label mean", or wants the branch and merge conventions Catalyst follows.
Retrieve GitHub Actions logs with gh, analyze failures, and fix CI errors locally.
Create or update a GitHub pull request with a standardized template. Use when the user wants to open a PR, create a pull request, update a PR description, submit changes, or push a PR.
Explain large or complex pull requests as a navigable HTML guide, tracing user journeys from entrypoints through changed code. Use when asked to understand a PR or build a guided walkthrough of its changes.
GitHub deep review: bugs, PRs, best fix, stale-or-real, read code first.
Plan and coordinate approved multi-task work from prose, issues, repository evidence, or an explicitly selected Project by grouping selected issues into coherent PRs, delegating implementation in reusable task worktrees, and delivering verified draft PRs with required native stacks for dependent PRs. Never merges.