菜单
Initializes git-agent for a repository — generates commit scopes from git history and .gitignore via AI. Use when the user asks to "configure git", "setup git", "set commit scopes", "update gitignore", "create gitignore", or needs project-specific Git settings.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | setup |
| description | Initializes git-agent for a repository — generates commit scopes from git history and .gitignore via AI. Use when the user asks to "configure git", "setup git", "set commit scopes", "update gitignore", "create gitignore", or needs project-specific Git settings. |
| user-invocable | true |
| argument-hint | [scope|gitignore] |
| model | haiku |
| allowed-tools | ["Bash(git-agent:*)","Bash(git:*)","Bash(ls:*)","Bash(find:*)","Read","Write","Edit","AskUserQuestion"] |
CRITICAL:
.gitignore rules before running git-agent init --gitignore.git-agent init command with --free appended.git config user.name and git config user.email; if either is missing, use AskUserQuestion tool to collect it from the user.$ARGUMENTS to determine mode:
scope → run only scope generationgitignore → run only .gitignore generation.gitignore already exists:
# --- git-agent --- markers or common auto-generated patterns)git-agent init with the appropriate flags:
git-agent init --scope --gitignore --forcegit-agent init --scope --forcegit-agent init --gitignore --force--free appended..gitignore rules were saved in step 3, append them back and show git diff .gitignore.CLI reference: ${CLAUDE_PLUGIN_ROOT}/references/cli.md
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.