pi: convert git-commit skill to /commit prompt template

Author: juanibiapina

…gents/.agents/skills/git-commit/SKILL.md dotfiles/pi/.pi/agent/prompts/commit.mddotfiles/agents/.agents/skills/git-commit/SKILL.md renamed to dotfiles/pi/.pi/agent/prompts/commit.md dotfiles/agents/.agents/skills/git-commit/SKILL.md renamed to dotfiles/pi/.pi/agent/prompts/commit.md

@@ -1,11 +1,10 @@
 ---
-name: git-commit
-description: Git commit workflow. Use when asked to commit changes or simply on the word `commit`.
+description: Create a git commit
 ---
 
 # Git Commit Workflow
 
-Only create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:
+Follow these steps carefully:
 
 Git Safety Protocol:
 - NEVER update the git config
@@ -18,7 +17,6 @@ Git Safety Protocol:
   (3) Commit has NOT been pushed to remote (verify: git status shows "Your branch is ahead")
 - CRITICAL: If commit FAILED or was REJECTED by hook, NEVER amend - fix the issue and create a NEW commit
 - CRITICAL: If you already pushed to remote, NEVER amend unless user explicitly requests it (requires force push)
-- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive.
 
 1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel, each using the Bash tool:
   - Run a git status command to see all untracked files.