Facilitate interactive brainstorming sessions for feature ideas using structured questioning rounds. Use when asked to "brainstorm", "explore an idea", "flesh out a feature", "help me think through", or when the user presents a raw feature concept that needs refinement. Guides users through metrics, visualization, goals, implementation details, and scope to produce a complete feature spec.
Review current changes with parallel subagents
Check GitHub pipeline status and plan fixes if failing
Interview me about the plan
Analyze conversation for learnings and save to docs folder
Open a pull request from the current branch
| name | push |
| description | Commit staged changes and push to remote |
| allowed-tools | Bash(git status), Bash(git diff:*), Bash(git log:*), Bash(git add:*), Bash(git commit:*), Bash(git push:*), Bash(git rev-parse:*), Bash(git remote:*) |
I have gathered information about your changes. Here are the results:
<git_status>
!git status
</git_status>
<staged_diff>
!git diff --cached
</staged_diff>
<unstaged_diff>
!git diff
</unstaged_diff>
<recent_commits>
!git log --oneline -10
</recent_commits>
<current_branch>
!git rev-parse --abbrev-ref HEAD
</current_branch>
<remote_info>
!git remote -v
</remote_info>
Analyze the diffs above to understand what changed.
Stage files if needed (skip already staged files, skip files that shouldn't be committed like .env).
Generate a conventional commit message following this format:
<type>(<scope>): <description>
[optional body]
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore
Create the commit using a HEREDOC for proper formatting:
git commit -m "$(cat <<'EOF'
type(scope): description
EOF
)"
Push to remote using the current branch:
git push origin <current-branch>
If the branch doesn't have an upstream, use:
git push -u origin <current-branch>
Show the result with git log -1 to confirm the commit, and verify the push succeeded.