3275 个 · 按相关度排序
Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
中文简介正在准备中。当前显示原文说明。
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.
中文简介正在准备中。当前显示原文说明。
Review PRs: diffs, inline comments via gh or REST.
中文简介正在准备中。当前显示原文说明。
Clone/create/fork repos; manage remotes, releases.
中文简介正在准备中。当前显示原文说明。
Evaluate and maximize GitHub repo quality from 7/10 to 10/10 perfect
中文简介正在准备中。当前显示原文说明。
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and crash-proof pipeline execution.
中文简介正在准备中。当前显示原文说明。
Create portfolios using Devsync template with automated CV, GitHub, LinkedIn, and academics generation
中文简介正在准备中。当前显示原文说明。
Create or update a GitHub pull request following Medox conventions (author spicode-bot, reviewer spideystreet). Invoke manually with /pr — do NOT trigger automatically.
中文简介正在准备中。当前显示原文说明。
Use when turning approved plans, specs, PRDs, or Epics into trackable GitHub Issues.
中文简介正在准备中。当前显示原文说明。
Use when the user asks for QA analysis, test planning, test cases, or root-cause analysis of a defect. Also use for post-merge PR review analysis: auditing recent closed PRs for Devin/GitHub/security bot comments, verifying whether requested corrections were applied, and turning pending fixes into SPECs.
中文简介正在准备中。当前显示原文说明。
Use when analyzing SonarQube issues and turning them into SPEC SDDs and tracked GitHub Issues for TDD implementation.
中文简介正在准备中。当前显示原文说明。
Use when auditing a repository for evidence-backed gaps between code, SPECs, architecture, and documentation — before a release, after a review, or when the user asks what is missing or divergent. Confirmed gaps become Draft SPECs via write-specs, a tracked GitHub Epic via create-issues, and orchestrated execution via orchestrator, with an explicit approval gate before any external action.
中文简介正在准备中。当前显示原文说明。
Govern discovery, eligibility, and submission of a plugin or skill to official directories, registries, marketplaces, and curated GitHub lists. Use when preparing or sending plugin listings, marketplace forms, directory PRs, or repository recommendations; require current policy evidence and a final human confirmation before every external submission.
中文简介正在准备中。当前显示原文说明。
Govern the SemVer release process — versioning discipline, tag-based GitHub releases, changelog hygiene, and the ADR that confirms the release strategy is agreed. Trigger when setting up a release process, before a first public release, or when release practice has become inconsistent. Owned by delivery-orchestrator.
中文简介正在准备中。当前显示原文说明。
Systematically find root causes and fix bugs. Use when debugging errors, investigating test failures, reproducing bugs from issue trackers (GitHub, Linear, Jira), or when stuck on a problem after failed fix attempts. Also use when the user says 'debug this', 'why is this failing', 'fix this bug', 'trace this error', or pastes stack traces, error messages, or issue references.
中文简介正在准备中。当前显示原文说明。
Run all code quality checks (security, complexity, test coverage) on the current PR and post a combined report as a GitHub PR comment. Use before merging a PR, during code review, or when asked to check code quality.
中文简介正在准备中。当前显示原文说明。
Create a git branch named after a GitHub issue.
中文简介正在准备中。当前显示原文说明。
Fix a GitHub issue by number. Reads the issue, implements a fix, and prepares a commit.
中文简介正在准备中。当前显示原文说明。
Run the complete release workflow: changelog entry, version bump, git tag, and GitHub release. Invokes changelog-entry, tag-version, and publish in sequence. Use when releasing a new version of the project.
中文简介正在准备中。当前显示原文说明。
Push the current branch and all tags to origin, then create a GitHub release using the latest tag and its CHANGELOG.md entry. Use after tag-version to complete a release.
中文简介正在准备中。当前显示原文说明。
Squash the current branch's work into a single commit and open (or update) a GitHub pull request with Graphite (`gt`). Use when asked to "create a PR", "open a pull request", "put this up for review", or to update an existing PR for the current branch.
中文简介正在准备中。当前显示原文说明。
TDD pair programming with mode switching. Claude can be driver (writes code) or navigator (watches, questions, provokes). Supports GitHub issues, file watching, or arbitrary prompts. Scientific TDD, baby steps, one test at a time. Trigger on: pair, let's pair, tdd, you drive, I'll drive, dojo.
中文简介正在准备中。当前显示原文说明。
Implementer - fetches a GitHub issue, builds an implementation plan, then implements using TDD. Use when: implement, build this, code this, add this feature, TDD, test first, red green refactor, pick a task, next task, dev.
中文简介正在准备中。当前显示原文说明。
Product Owner - scans codebase and creates or amends GitHub issues with PRD. Use when: PRD, feature, issue, create issue, amend issue, what should we build, plan feature, design feature, scope, requirements, user story.
中文简介正在准备中。当前显示原文说明。