Loading...
Loading...
Found 2,464 Skills
Use when the user wants to automate WeChat mini-program upload, preview, or npm packaging via CI/CD, generate deployment scripts, set up miniprogram-ci workflows, or create preview QR codes automatically. Trigger whenever the user mentions "上传小程序", "预览", "CI 部署", "miniprogram-ci", "自动化上传", "发布小程序版本", "生成预览二维码", "打包npm", "pack-npm", "构建npm依赖", "GitHub Actions 小程序", "pnpm 小程序部署", or asks to integrate WeChat mini-program with continuous integration pipelines (GitHub Actions, GitLab CI, etc.).
Issue creation workflow for Agent Teams Lite following the issue-first enforcement system. Trigger: When creating a GitHub issue, reporting a bug, or requesting a feature.
Validates recently written code against project-specific development guidelines from .trellis/spec/. Identifies changed files via git diff, discovers applicable spec modules, runs lint and typecheck, and reports guideline violations. Use when code is written and needs quality verification, to catch context drift during long sessions, or before committing changes.
Delegate coding tasks to Google Jules AI agent for asynchronous execution. Use when user says: 'have Jules fix', 'delegate to Jules', 'send to Jules', 'ask Jules to', 'check Jules sessions', 'pull Jules results', 'jules add tests', 'jules add docs', 'jules review pr'. Handles: bug fixes, documentation, features, tests, refactoring, code reviews. Works with GitHub repos, creates PRs.
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.
Sync local changes to GitHub in one command: detect state, branch, commit, push, create PR. Use when user wants to push work to GitHub, create a PR, or sync a feature branch. Use for "push my changes", "create a PR", "sync to GitHub", "open pull request", or "ship this". Do NOT use for reviewing PRs (use /pr-review), cleaning up after merge (use pr-cleanup), or CI checks (use ci).
Coordinate PR mining to extract tribal knowledge and coding standards from GitHub PR history. Use when mining review comments, extracting coding rules, tracking mining jobs, or analyzing reviewer patterns across repositories. Use for "mine PRs", "extract standards", "coding rules from reviews", or "reviewer patterns". Do NOT use for code review, linting, static analysis, or writing new coding standards from scratch without PR data.
Deterministic 3-phase GitHub PR review comment extraction: Authenticate, Mine, Validate. Use when mining tribal knowledge from PR reviews, extracting coding standards from review history, or building datasets for the Code Archaeologist agent. Use for "mine PRs", "extract review comments", "tribal knowledge", or "PR review history". Do NOT use for analyzing patterns, generating rules, or interpreting comments — that is the Code Archaeologist agent's responsibility.
Restore session state from handoff artifacts and route to the next action. Priority cascade: HANDOFF.json (highest) > .continue-here.md > incomplete task_plan.md > git log. Presents a status dashboard, then executes the next action. Use for "resume", "continue", "pick up where I left off", "what was I doing", "continue work". Do NOT use for starting new tasks (use /do), reviewing past sessions (use /retro), or reading task plans (read task_plan.md directly).
Create session handoff artifacts (HANDOFF.json + .continue-here.md) that capture completed work, remaining tasks, decisions, uncommitted files, and reasoning context so the next session can resume without reconstruction overhead. Use for "pause", "save progress", "handoff", "stopping for now", "end session", "pick this up later". Do NOT use for task planning (use task_plan.md), session summaries (use /retro), or committing work (use /commit or git directly).
Post-mortem diagnostic analysis of failed or stuck workflows. Detects stuck loops, missing artifacts, abandoned work, scope drift, and crash/interruption patterns through git history and plan file analysis. Produces a structured diagnostic report with anomaly confidence levels, root cause hypotheses, and recommended remediation. READ-ONLY: never modifies files. Use for "forensics", "what went wrong", "why did this fail", "stuck loop", "diagnose workflow", "post-mortem", "workflow failure", or "session crashed". Do NOT use for debugging code bugs (use systematic-debugging), reviewing code quality (use systematic-code-review), or fixing issues (forensics only diagnoses).
Fetch PR feedback from all GitHub sources and validate every comment before acting. Use when user needs to process PR review comments, address reviewer feedback, or triage pull request discussions. Use for "review comments", "PR feedback", "address reviews", "address feedback", or "what did reviewers say". Do NOT use for creating new PRs, code review of local changes, or general code analysis without an existing PR.