القائمة
Resolves GitHub issues using isolated worktrees and test-driven development. This skill should be used when the user asks to "resolve an issue", "fix issue
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Reviews SwiftUI code for best practices on modern APIs, maintainability, and performance. This skill should be used when the user asks to review SwiftUI code, check for deprecated iOS/macOS APIs, validate data flow patterns, or audit accessibility compliance in Swift projects.
Provides the shared STORM methodology, artifact layout, stage-gating contract, citation hygiene, and retrieval fallback. Use when executing any /storm:* skill (generate, research, outline, write, polish). Internal knowledge; never user-invocable.
Run the full STORM pipeline end-to-end. This skill should be used when the user asks to "generate a storm article", "write a wikipedia-style article about X", "research and write a long-form piece on X", or invokes /storm:generate. Orchestrates research -> outline -> write -> polish, skipping already-completed phases.
Run STORM phase 2 — outline generation. This skill should be used when the user asks to "generate an outline for a storm article", "draft a wikipedia-style outline", or invokes /storm:outline. Produces a draft outline from parametric knowledge then refines it using the research information table.
Run STORM phase 4 — article polishing. This skill should be used when the user asks to "polish the storm article", "finalize the article", or invokes /storm:polish. Adds a summary section, removes duplicate content, and verifies citation integrity.
Run STORM phase 1 — multi-perspective research. This skill should be used when the user asks to "research a topic for an article", "find sources on X from multiple perspectives", "do storm research on X", or invokes /storm:research. Discovers personas, runs simulated Q&A per persona in parallel, and produces an information table + deduplicated sources.
| name | resolve-issues |
| allowed-tools | Bash(gh:*), Bash(git:*), EnterWorktree, ExitWorktree, Task |
| description | Resolves GitHub issues using isolated worktrees and test-driven development. This skill should be used when the user asks to "resolve an issue", "fix issue |
| argument-hint | ["issue number or description"] |
| user-invocable | true |
Execute issue resolution workflow using isolated worktrees, TDD methodology, and agent collaboration.
git statusgit branch --show-currentgit worktree listgh issue list --state open --limit 10gh auth statusUse isolated worktrees to avoid disrupting main development. Follow TDD cycle (red → green → refactor) with agent support. Reference issues in commits using auto-closing keywords. See references/requirements.md for protected PR workflow and commit standards.
Goal: Select target issue and prepare isolated development environment.
Actions:
$ARGUMENTSfix-456-auth-redirect) to create an isolated sessiongit branch -m <type>/<issue>-<description> (see references/workflow-details.md for naming)Goal: Implement fix using test-driven development with agent collaboration.
Actions:
references/workflow-details.md for project-specific checks)Goal: Create pull request, link issue, and clean up worktree after merge.
Actions:
git push -u origin <branch-name>gh pr create with auto-closing keywords (e.g., "Closes #456"). CRITICAL: Auto-closing keywords only trigger when the PR merges into the repository's default branch. If targeting a non-default branch (e.g. develop), warn the user that the issue will NOT close automatically on merge and must be closed manually.
--draft if the fix requires further feedback before reviewreferences/requirements.md - Worktree setup, TDD, and commit standardsreferences/workflow-details.md - Issue selection, TDD cycle, agent collaborationreferences/examples.md - Commit message examples