Loading...
Loading...
Found 1,433 Skills
Initialize the .specify/ directory structure for Spec-Driven Development in the current project
Identify and report potentially malicious software repositories masquerading as legitimate security tools
This skill should be used when the user says "get PR comments", "show PR feedback", "what comments on my PR", "PR review comments", "show me the review", "what did reviewers say", or asks about feedback on a pull request. Not for creating PRs or responding to comments.
Triage and orchestrate code reviews. Analyzes PR intent, identifies touched surfaces, assesses risk, and routes to specialist skills. Does NOT perform detailed review - delegates to specialists. Supports full pipeline with "Review PR <number>" command.
Use when preparing a pull request for merge: inspect diffs, collect checks and review comments, classify findings, fix safe issues, verify, and loop until merge-ready.
CLI for bootstrapping and managing wordspace projects
Full guided pipeline — scaffold, design, audio, deploy, and monetize a game from scratch
DevOps workflows for Playwright - CI failure analysis, workflow debugging, and release operations.
Use when a PR has reviews and is ready for final validation, to verify minimum 3 different agents reviewed and no critical concerns were raised before merging
Render the current plan as a high-DPI PNG dependency DAG — nodes are issues / sub-issues / PRs, edges come from sub-issue links plus dependency-language prose ("Depends on", "Part of", "Blocks", "Closes") and PR / commit cross-references, and every node is color-coded done / in-progress / available-next / blocked so sequencing and critical path are obvious at a glance. Use when asked "plan as dag", "draw a dag", "dag diagram", "show the dependency graph", "what's blocking what", "what's the critical path", "what can be parallelized", "what's left for
Detect and analyze potentially malicious repositories disguising as legitimate software cracks or pirated tools
Open a pull request the bklit-ui way: stage and commit with pre-commit hooks, run ultracite from the repo root, run a production test build, fix failures, push, and create a PR with a structured summary. Use when the user asks to commit, push, open a PR, "ship it", or run the full pre-PR checklist.