[Feature]: git extension: scope the after_implement auto-commit to the files the command changed #5025

Activity

1. mnriem commented on Oct 19, 2026

   

   mnriem

   on Oct 19, 2026

   Collaborator

   More actions

   Thanks for the detailed proposal. Yes, this can be delivered as your own preset.

   Presets sit above extensions in the resolution stack and can override both the core speckit.implement command and the git extension's speckit.git.commit command. The preset could declare the git extension dependency and provide these command replacements:

   requires:
     speckit_version: ">=1.2.1"
     extensions:
       - git
   
   provides:
     templates:
       - type: command
         name: speckit.implement
         file: commands/speckit.implement.md
         strategy: wrap
   
       - type: command
         name: speckit.git.commit
         file: commands/speckit.git.commit.md
         strategy: replace

   The speckit.implement wrapper would preserve the standard implementation instructions while requiring the agent to write the paths it created, modified, renamed, or deleted to a temporary manifest, for example .specify/tmp/after-implement-paths.

   The replacement speckit.git.commit command could then use that manifest only for the after_implement event:

   git add --pathspec-from-file=.specify/tmp/after-implement-paths
   git commit -m "$message"
   rm -f .specify/tmp/after-implement-paths

   Other hook events could continue invoking the existing git extension script, preserving its current behavior.

   The key requirement is that the implementing agent must produce the path list. The commit hook cannot derive file ownership from git status, because unrelated working-tree changes are indistinguishable by then.

   Given that this is an opt-in workflow policy and can be implemented without changing the hook contract or default auto-commit behavior, a separately maintained preset—potentially published as a community preset—is the appropriate solution, so I am closing this as not planned for the first-party git extension.

   AI disclosure: Posted on behalf of @mnriem with GitHub Copilot using GPT-5.6 Sol in human-supervised agent mode; Copilot assessed preset feasibility and drafted this maintainer response.
2. mnriem

   closed this as not plannedon Oct 19, 2026