Loading...
Loading...
Found 26 Skills
Triage and resolve repository GitHub issues using the bundled CLI. Use when asked to read issue state, discuss issue scope, implement issue-driven code changes, post comments, or close issues.
Enabled when investigating and isolating the cause of a problem
Executes web app workflows in Safari on the iOS Simulator from /workflows/ios-workflows.md. Use this when the user says "run ios workflows", "execute ios workflows", or "test ios workflows". Tests each workflow step by step in mobile Safari, captures before/after screenshots, documents issues, and generates HTML reports with visual evidence of fixes.
Issue Workflow Stage 3——Fix code precisely based on confirmed root cause and solution, verify the effect, and document it in {slug}-fix-note.md. This is the final stage of the issue workflow—no verification loop means the workflow is incomplete. Two entry points: the standard path is triggered from easysdd-issue-analyze (with existing {slug}-analysis.md), and the quick path is triggered directly from easysdd-issue-report (without {slug}-analysis.md, as the root cause was determined by AI reading code during the report stage). Trigger scenarios: user says 'Start fixing the bug', 'Fix according to analysis', 'Start modifying code'. During repair, only modify the files stated in the solution; do not optimize casually or introduce new abstractions—these actions will make the scope spread to untraceable levels.
Fix all open GitHub issues labeled `internal request` in isolated worktrees, then open PRs
Unified team skill for issue resolution. All roles invoke this skill with --role arg for role-specific execution. Triggers on "team issue".
Diagnose and fix plugin registry issues including orphaned entries and project-scope conflicts (addresses Claude Code issue
Structured debugging skill for methodical root cause analysis. Use when investigating bugs, unexpected behavior, or errors. Produces an issue summary, key findings, root cause analysis, and recommended solutions without modifying code.
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
Root-cause-driven solution decision framework for the hardest problems across any domain. This is the nuclear option — it consumes significant tokens through exhaustive multi-branch root cause analysis, MECE solution enumeration, and domain-adaptive external validation. Use ONLY for genuinely difficult problems: recurring failures that resist repeated fix attempts, complex systemic issues with no clear solution path, decisions where multiple approaches exist and the wrong choice has high cost, problems with multiple interacting causes spanning components or teams. Trigger when: the user says 'what's the best way to fix X', 'why does this keep happening', 'how should we approach this', 'find the root cause', 'what are my options for fixing X', 'analyze this problem systematically', 'evaluate our options for X', 'what's the right approach and why', or expresses frustration that previous solutions didn't stick. Do NOT use for: problems where the answer is already obvious or requires no analysis, straightforward issues with clear solutions, or routine investigation. If the problem can be solved in 5 minutes of investigation, this skill is overkill.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Unified issue resolution pipeline with source selection. Plan issues via AI exploration, convert from artifacts, import from brainstorm sessions, form execution queues, or export solutions to task JSON. Triggers on "issue:plan", "issue:queue", "issue:convert-to-plan", "issue:from-brainstorm", "export-to-tasks", "resolve issue", "plan issue", "queue issues", "convert plan to issue".