Loading...
Loading...
Found 8,774 Skills
Create pull requests with Conventional Commit-style titles and template-compliant descriptions using GitHub CLI. Use when asked to create, open, draft, or update a PR from the current branch and the team expects consistent semantic titles and structured PR bodies.
tRPC router architecture, procedure design, and Vertical Slice Architecture patterns. Use when building tRPC APIs, designing procedures, or structuring backend slices.
Check and configure GitHub Pages deployment
Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on GitHub, and has GitHub Actions CI with automated checks (lint, build, tests, etc.). Does NOT merge - stops when CI passes and provides the PR link.
Create GitHub issues using data-driven templates. Supports any issue type via configurable template configs. Use when the user asks to create a GitHub ticket, issue, or support ticket, or when they want to add a new issue template.
Guide wanderers to the right animal for their journey. Perch, tilt your head, chatter about the forest, present the options, and warble the recommendation. Use when helping users choose which skill to use, discovering capabilities, or navigating the ecosystem.
Generate a gold-standard README for any project. Interviews you about the problem, generates a draft following battle-tested patterns, then council-validates it. Triggers: "readme", "write readme", "generate readme", "improve readme", "rewrite readme".
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Push commits and create/update pull request
Build the project, commit all changes, and deploy directly to main. Use when deploying changes to production.
Review, organize, and commit pending changes. Split into logical commits, stage carefully, and write clear Conventional Commit messages. Use when the user asks to commit, stage changes, or organize work into commits.
Best practices for developing, deploying, and debugging Supabase Edge Functions (Deno runtime). Use when working with Edge Functions for tasks like ingest pipelines, webhooks, scheduled jobs, or database triggers. Covers authentication patterns (service role vs anon key), error debugging, database integration, and common pitfalls.