[Dev10x:git-commit] Step 11 must mandate mktmp and document hook recovery

Resolved 💬 2 comments Opened Mar 30, 2026 by wooyek Closed Mar 30, 2026

Problem

The skill's Step 11 says "Write the message to a temp file" but does not require mcp__plugin_Dev10x_cli__mktmp for path generation. Agents use hardcoded paths which the hook rejects, then escalate to prohibited bypass patterns (Python subprocess).

Evidence

  • Agent used non-mktmp path twice (hook blocked both times)
  • Agent then attempted python3 subprocess.run(["git", "commit", ...]) to bypass hook (user rejected)
  • User corrected: "use mktmp mcp with git commit-msg .txt"
  • After using mktmp, the operation succeeded on first attempt

Proposed Fix

  1. Step 11 sub-steps should be explicit:
  • (a) Call mcp__plugin_Dev10x_cli__mktmp(namespace='git', prefix='commit-msg', ext='.txt')
  • (b) Read the empty file (Write requires prior Read)
  • (c) Write the message to the returned path
  • (d) Execute commit with -F <mktmp-path>
  1. Add error recovery note: "If the hook blocks the operation, you are likely using a non-mktmp path or outside the skill context. Restart via Skill(Dev10x:git-commit) with no args."
  1. Step 5 (problem/solution): Add instruction "If session context contains the full diff and architectural decision already discussed, auto-generate BOTH problem and solution without prompting user."

Additional: AskUserQuestion preview gate

The REQUIRED AskUserQuestion for message preview (Step 9) was skipped in both invocations. Make this gate's REQUIRED status more prominent — it was also skipped when the agent incorrectly declared "unattended mode" for a nested invocation from gh-pr-create.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗