Loading...
Loading...
Found 40 Skills
The skill to revert unnecessary changes and leave only essential changes when a user requests a cleanup of changes, or before committing and creating a pull request.
Use for the Team pipeline only on explicit request. Never infer from ordinary coding work. Runs QRSPI or a leading route.
Diagnose and fix slow Paperclip PostgreSQL queries using Cloud and Neon evidence, local reproduction, performance and result comparisons, regression tests, and a PR with passing checks. Use for costly queries, repeated database work, or slow requests with a suspected database cause.
Use when explicitly asked to deliver an approved GitHub or local spec through a reviewed pull request, or when a Project controller delegates one claimed implementation ticket.
Implement or review code through a verified result. Keep changes small and TypeScript readable.
Takes a change all the way from code to a merged pull request without supervision: build it, prove it, review it, file the PR, watch it and merge it. Use when the user says ship it, send it all the way, merge when green, or /ds-ship.
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments. Identical to greploop, but triggers reviews by tagging @greptile-apps, which bypasses Greptile's file-count limit on huge PRs that the plain @greptile mention refuses to review. Use when the user wants to fully optimize a large PR/MR/CL against Greptile's code review standards.
Run one exact Ticket through recovery and autonomous work to a ready pull request, keeping its Manifest, progress and completion record on that same Ticket, and land it only when told to. Use when orchestrate, an agent runner, or a person supplies a specific issue, tracker item, or file Ticket to work end to end. This skill does not select backlog work or enforce Auto eligibility at dispatch.
Build an internally reviewed feature plan from its shared folder, prove the draft pull requests and run code review.
PDD small-change workflow. Use when the change stays outside PDD (docs, guides, packages, config, CI, lockfiles or test maintenance — never prompts, Stories or product code), also when written as a bug. Plan it, make it, verify it, one PR.
Writes work-in-progress code and tests based on design doc
Continuously improve Remotion Studio by making a video, reproducing real UX and performance issues, fixing them, and verifying the result. Use for ongoing Studio dogfooding and maintenance, including checkpoints that hand one PR over for review while work continues in a stacked PR.