Loading...
Loading...
Found 3,997 Skills
Create a PR with dev as base using the pull request template. Use when opening a new PR.
Generate commit messages following conventional commits and commit staged changes. Use when creating commits or when user invokes /commit.
Generates clear, actionable verification guides for QA testing of Positron bug fixes and features
Loads org- and repo-level coding rules from Qodo before code tasks begin, ensuring all generation and modification follows team standards. Use before any code generation or modification task when rules are not already loaded. Invoke when user asks to write, edit, refactor, or review code, or when starting implementation planning.
Run /check-quality, then fix the highest priority quality issue. Creates one fix per invocation. Invoke again for next issue. Use /log-quality-issues to create issues without fixing.
Create conventional commit messages by analyzing staged changes. Generates semantic commit messages following the Conventional Commits specification. Use when user says "commit", "save changes", or "create commit".
Write READMEs for software projects. The skill should be used when writing or revising a README or README.md file.
Find similar or analogous code patterns elsewhere in a codebase. Use when answering "Do we do something similar elsewhere?" or "What existing patterns match this?" Returns factual findings about similar code - locations, similarity type, and confidence.
Analyze completed Ralph worktree branches, build a smart merge priority queue, and sequentially squash-merge them into main with worktree cleanup. Use this skill whenever the user wants to merge ralph worktrees, merge completed features, clean up finished ralph branches, process the ralph merge queue, or asks about which ralph branches are ready to merge. Triggers on: merge worktrees, ralph merge, merge completed branches, ralph cleanup, merge queue, which branches are done, squash ralph branches.
Run all groove health checks: config, backends, companions, AGENTS.md.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup."
ALWAYS use this skill when creating or updating pull requests — never create or edit a PR directly without it. Follows Sentry conventions for PR titles, descriptions, and issue references. Trigger on any create PR, open PR, submit PR, make PR, update PR title, update PR description, edit PR, push and create PR, prepare changes for review task, or request for a PR writer.