tool-synthesis

You can create per-worktree scratch tools by authoring a small executable inside the worktree, registering it in a per-worktree registry, and calling it from Bash. A cleanup gate ensures the scratch tools are removed before merge to prevent main branch contamination.

Per-worktree isolation stores scratch tools under a dedicated worktree path with a per-worktree registry.json for auditability, ensuring tools remain scoped to a single worktree and do not leak into the main codebase.

Yes, per-worktree scratch tools support automated pipelines for repo-specific tasks such as fast searches and quick analyses. They are stored under an isolated worktree path and a cleanup gate ensures they disappear after use.

Automatic gitignore protection and a mandated cleanup gate prevent scratch tools from leaking into main branches. Per-worktree isolation ensures the tools are scoped to a single worktree and removed before merge.

The best way to manage one-off bash executables is using per-worktree scratch tools with a registry.json for auditability and executable permissions. This approach provides isolation and a cleanup gate to ensure tools disappear after use.