Loading...
Loading...
Found 34 Skills
Conversational bug discovery → issue draft. Light listening, background exploration, scope assessment. Asks before gh issue create — never auto-files. Use when conducting a QA session, triaging user-reported issues, or filing bugs.
Verify that a pull request or local changes fully implement the requirements described in a linked GitHub issue. Use when asked to "verify PR 123", "verify my changes", "check PR #123 coverage", "verify PR #123 against issue #42", "check local changes", or "do my changes cover issue 42". Analyzes the diff against issue requirements and reports either missing items or confirms 100% coverage.
Implement a feature from issue, specs, and docs, then propose a PR
Run /check-landing, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-landing instead if you want to fix issues immediately.
Run /check-stripe, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-stripe instead if you want to fix issues immediately.
Create Linear tickets or GitHub issues following n8n conventions. Use when the user asks to create a ticket, file a bug, open an issue, or says /create-issue.
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Use when user asks to "discover tasks", "find next task", or "prioritize issues". Discovers and ranks tasks from GitHub, GitLab, local files, and custom sources.
Use this skill to triage a single newly opened, reopened, or `status/needs-triage`-labelled issue in microsoft/apm. Emit one synthesized comment with a triage decision, label set, milestone, and suggested next action.
Use when running an infra-only health audit across Pylot systems — LaunchAgent, cron, secrets, labels, branches, and issues.