Loading...
Loading...
Found 49 Skills
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.
Triage a bug report. Reproduces the bug, diagnoses the root cause, verifies whether the behavior is intentional, and attempts a fix. Use when asked to "triage issue
Use when bootstrapping skill-loop in a repository, creating a GitHub issue loop starter, or writing and updating skill-loop.yml and starter skills.
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.
Implement one ready-for-agent GitHub issue end to end and open a reviewed pull request.
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.
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.
Use gitcrawl for OpenClaw issue and PR archive search, duplicate discovery, related-thread clustering, and local GitHub mirror freshness checks.
Create a detailed refactor plan with tiny commits through user interviews, then file it as a GitHub issue. Use this when the user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
Interactive backlog grooming. Explore, brainstorm, discuss, then synthesize. Orchestrates agents and issue-creator skills. Creates prioritized GitHub issues. Enforces Misty Step org-wide standards.
Report a bug in the compound-engineering plugin
Embed screenshots, images, diagrams, GIFs, and screen recordings in GitHub PRs and issues — or stage them ahead of a PR, collect them into one attachments comment, or get a durable public link to share a visual with a person. Use this whenever a visual needs to end up in a PR description, issue body, or PR/issue comment, in front of a teammate, or saved for a PR that doesn't exist yet. Triggers include "attach a screenshot to the PR", "add a before/after to the issue", "include a screenshot of …", "share a GIF of the flow", "record the bug and put it in the issue", "get me a link I can paste in Slack", "stage screenshots for the PR", "attach this when I open the PR", "save this for the PR", "collect the PR's media", or having just captured or changed something visual that a shot would make clearer — even mid-task, before a PR exists. Also applies when an agent has no local filesystem and is uploading via the hosted MCP (agents.uploads.sh). Reach for this instead of drag-and-drop or github.com/user-attachments (agents can't upload there) and instead of hand-rolling cloud-storage uploads. Capture the visual with whatever browser or screenshot tooling you have; this skill covers hosting and embedding it.