Loading...
Loading...
Found 134 Skills
You are a GitHub issue resolution expert specializing in systematic bug investigation, feature implementation, and collaborative development workflows. Your expertise spans issue triage, root cause an
GitHub Discussion CLI for AI agents. Turn-based conversations on GitHub issues between Claude Code, Codex, and other agents.
Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.
Analyze GitHub issues by link or issue number. Use when a user says "analyse issue"/"analyze issue" or provides a GitHub issue URL/number and asks to fetch the issue content, verify it matches the current repo, and inspect local code to confirm the problem.
Template management system for code boilerplates, feedback templates, scaffolding, and project optimization workflows. Use when creating code templates, generating boilerplate files, managing project scaffolding, optimizing template performance, or preparing GitHub issue templates. Do NOT use for SPEC document creation (use moai-workflow-spec instead) or documentation generation (use moai-workflow-project instead).
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.
Create GitHub Issue from spec documents — Auto-generate structured Feature Issues from specifications. Analyzes spec documents (requirement.md, design.md, tasks.md) in .specs/{feature}/ and generates a structured Feature Issue via gh issue create. Best used with specs created by spec-generator. English triggers: - "Create issue from spec", "Register spec as issue" - "Convert spec to GitHub issue", "Publish spec to issue" - After spec-generator: "Turn this into an issue" 日本語トリガー: - 「仕様書をIssueにして」「Issueに登録して」「specからIssue作成」 - 「仕様書からIssue生成」「specをIssueに変換」 - spec-generator完了後に「これをIssueにして」「Issueにして」
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
Analyze Azure resources used in the app (IaC files and/or resources in a target rg) and optimize costs - creating GitHub issues for identified optimizations.
Fetch a GitHub issue body and its messages as YAML for the current repository.
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'.
Report a bug in the compound-engineering plugin