Loading...
Loading...
Found 236 Skills
Cluster a GitHub issue backlog by root cause into a small set of plan-master issues, redirect children with a standardized comment, and bundle architectural-fix PRs that close clusters atomically. Use when an issue tracker has accumulated dozens of reports that share underlying defects, when asked to triage / consolidate / cluster / dedupe issues, when asked to build a plan series or roadmap from open issues, or when routing a new incoming bug into an existing plan.
Run a GitHub issue digest for openai/codex by feature-area labels, all areas, and configurable time windows. Use when asked to summarize recent Codex bug reports or enhancement requests, especially for owner-specific labels such as tui, exec, app, or similar areas.
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.
Analyze a user-provided Git repository and GitHub issues to confirm contribution rules (CONTRIBUTING, CLA/DCO, templates) and shortlist high-value, maintainer-friendly issues likely to be accepted. Use when a user wants help selecting open-source issues to contribute to, or when triaging a GitHub repo for good first contributions.
This workflow guides you through a systematic approach to identify missing features, prioritize them, and create detailed specifications for implementation.
Use when an issue needs deeper analysis than triage — confirming root cause by reading code, verifying file/line references in body are still valid, checking blast radius across the codebase, or proposing a concrete fix direction. One issue per invocation.
Collect and submit feedback about Superset — bug reports, feature requests, or general feedback — privately to the Superset team or as a public GitHub issue. Use when the user wants to report a Superset bug, request a feature, or send feedback about Superset.
Organize, desensitize, and report GitHub bugs for chengfeng-videocut. Use this when the user requests to report a bug, provide feedback on clip voiceover issues, submit a GitHub Issue, inform developers about the problem, or request to continue submitting a pre-viewed bug draft. Do not use it for feature suggestions, general troubleshooting, code submissions, or automatic reporting without user confirmation.
Builds a project and Ship it to the target environment
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).
Interactive backlog grooming. Explore, brainstorm, discuss, then synthesize. Orchestrates agents and issue-creator skills. Creates prioritized GitHub issues. Enforces Misty Step org-wide standards.
AI-Native Issue-Driven development workflow. From GitHub Issue to merged PR: parse issue, explore codebase, design technical plan, execute with agent team, create PR, and cleanup. Use when a user wants to implement a GitHub Issue end-to-end: `/issue-flow #123` or `/issue-flow` to pick from open issues.