Loading...
Loading...
Found 66 Skills
Detect duplicate GitHub issues using semantic search and keyword matching. Use when asked to find duplicates, check for similar issues, or set up automated duplicate detection.
Run /check-docs, then create GitHub issues for all findings. Issues are created with priority labels and structured format. Use /fix-docs 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.
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.
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.
Convert tasks.md into GitHub issues in the current repository
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.
Create a GitHub issue in a mitodl repository using the organization's standard issue templates. Triggered by /olissue — prompts for repo, issue type, and fills in the appropriate template (Bug Report, Technical, Product, Design QA). Defaults the organization to mitodl.
GitHub Issues-first workflow with sub-issues hierarchy. TRIGGERS - issue hierarchy, sub-issues, issue tracking, research workflow, cross-repo issues.
Workflow Checkpoint Basic Capabilities (Focus on Save and Resume): Record checkpoint progress and resume context in GitHub Issues. Applicable to any workflow stage, supporting automatic triggering and high-frequency manual calls. Keywords: save, resume, checkpoint, issue.
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.