feat(skills): add batch bundled skill#162
Merged
emal-avala merged 1 commit intomainfrom Apr 22, 2026
Merged
Conversation
Applies the same change across multiple git worktrees — each target in its own isolated worktree, test+lint gate per target, first failure stops the run so the user can decide. Prompt rules: - one worktree per target (don't mutate the current tree) - adapt the patch per target if file layout differs — don't paste blindly - stop on first failure and surface what broke - leave worktrees in place for inspection - never force-push, never skip tests
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds `/batch` — applies the same change across multiple git worktrees using the existing `worktree` tool.
Guarantees baked into the prompt:
Ends with a summary table: `target | commit or failure | files changed`.
Why
Common chore: "apply this fix to release branches 1.14, 1.15, 1.16". Without a skill, the agent tries to do them in the same working tree and either clobbers state or skips the test gate. This codifies the right workflow once.
Leans on `worktree` / worktree-aware sandbox policy that already exist.
Test plan