Loading...
Loading...
Found 236 Skills
Trier un bug ou une issue en explorant le codebase pour trouver la cause racine, puis créer une issue GitLab ou GitHub avec un plan de correction basé sur le TDD. À utiliser quand l'utilisateur signale un bug, veut créer une issue, mentionne « triage » ou veut investiguer et planifier la correction d'un problème.
Analyze GitHub issue content, assess its priority, identify missing information, and provide clear reproduction steps or triage advice. Trigger when the user asks to triage an issue, analyze a bug report, or asks 'how should I respond to this issue'.
Use gitcrawl for OpenClaw issue and PR archive search, duplicate discovery, related-thread clustering, and local GitHub mirror freshness checks.
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
Use when assessing whether a repo is ready for autonomous AI agents (pylot workers) — produces a scored, actionable Agent Readiness Report as a GitHub issue in the assessed repo.
End-to-end GitHub issue workflow: analyze the issue, plan and implement, verify with available tests/build/lint and an optional live observation, simplify, audit the tests it added, attack the change with parallel adversarial reviewers and fix what they find, trim comments and artifacts, then choose a push / PR / merge endgame — holding the merge while Copilot and other automated reviewers report, and answering and resolving their threads. The lifecycle's git and GitHub writes are delegated to `issue-flow`, the review threads to `pr-review`.
Use when brainstorming a feature or change whose spec should land in a GitHub issue instead of a docs/ file — including starting, pausing, and resuming a brainstorm across multiple sittings. The issue is created early as a [DRAFT] and becomes the durable spec; implementation happens separately later. Triggers include "brainstorm this into an issue", "spec it out as a GitHub issue", "file an issue for this feature", "continue/resume brainstorming issue
Run /check-virality, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-virality instead if you want to fix issues immediately.
Outputs markdown digests and CSV exports for GitHub issues and PRs. Use when creating status reports, weekly updates, stakeholder briefings, generating GitHub comment digests, tracking initiative health. Do not use when release gates/readiness - use release-health-gates. DO NOT use when: project planning - use spec-kit:speckit-orchestrator.
Interact with GitHub issues - create, list, and view issues.
Audit PostHog survey SDK features and version requirements
Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe). Use after /prd (and optionally /prd-to-spec) to turn requirements into actionable tickets. Triggers on: create issues, to-issues, 创建issue, 拆解issue, 生成卡片, 创建卡片, generate issues from PRD, issues from spec.