[Feature]: Evaluate git tool scope in workflow commands

[sjnims]

Problem or Need

The workflow commands (create-plugin.md and create-marketplace.md) currently allow only Bash(git init:*) in their allowed-tools. However, Phase 4 of both workflows mentions:

"Initialize git repo if creating new directory"

For a complete git initialization workflow, users might expect additional operations like:

• git add . to stage initial files
• git status to verify state
• git commit -m "Initial commit" for the first commit

Currently, only git init is permitted.

Proposed Solution

Evaluate and choose one of these approaches:

Option A: Expand git scope

allowed-tools: ..., Bash(git:*)

Option B: Add specific subcommands needed

allowed-tools: ..., Bash(git init:*), Bash(git add:*), Bash(git status:*), Bash(git commit:*)

Option C: Document intentional limitation
Keep current scope and document that file creation uses Write tool, so git operations are intentionally minimal.

Component

• Type: Command
• Specific: /plugin-dev:create-plugin, /plugin-dev:create-marketplace

Alternatives Considered

• Keep current scope: The Write tool handles file creation, so git add may not be needed within command execution. Users can run git commands after the workflow completes.
• Use hooks: A PostToolUse hook could handle git operations after Write tool usage

Additional Context

Current frontmatter:

allowed-tools: Read, Write, Edit, Grep, Glob, Bash(mkdir:*), Bash(git init:*), TodoWrite, AskUserQuestion, Skill, Task

The current design may be intentionally minimal to:

1. Keep commands focused on structure creation
2. Let users control their git workflow
3. Avoid assumptions about commit preferences

Priority

Low - Just a suggestion (may be intentionally limited)

[sjnims]

PR submitted: #139