Loading...
Loading...
Found 90 Skills
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Use this skill when user wants to create a refactor plan.
Triage a bug or issue by exploring the codebase to find root cause, then create a GitHub issue with a TDD-based fix plan. Use when user reports a bug, wants to file an issue, mentions "triage", or wants to investigate and plan a fix for a problem.
Send Antithesis feedback about the skills
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
Hand a Prisma Next question or report off to the team — file a GitHub issue (bug or feature request), or route Q&A / design discussion / direct-team-contact to the Prisma Discord at pris.ly/discord. Use for bug, bug report, file an issue, report a bug, feature request, missing feature, this should be a feature, file this, this is a bug, this is broken, surprising behaviour, this doesn't work, file feedback, send feedback, capability gap, file via prisma-next-feedback, ask the team, talk to the team, talk to the Prisma team, talk to Prisma, Discord, Prisma Discord, Q&A, design feedback, is this the intended way, how should I do X, extension author question, extension author needs help.
Files structured GitHub bug reports for agent-validator when users ask to file, report, or open an issue for a suspected defect
Create GitHub Issues with a parent-child structure (sub-issues). Generate parent and child issues using `gh issue create`, and link the parent-child relationship with `gh api .../sub_issues`. It is recommended to use Conventional Commits format (`feat:`, `fix:`, etc.) for titles. Used for scenarios like "Create an Issue" and "Break down tasks into Issues".
Use when running an infra-only health audit across Pylot systems — LaunchAgent, cron, secrets, labels, branches, and issues.
Deterministic feedback processor. Fetches client feedback emails from Gmail, downloads attachments (screenshots), and prepares a structured report for triaging into GitHub issues.
Create a GitHub issue with title and description. Use when the user wants to file a bug, request a feature, or create a tracking issue.
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.