Skip to content

A tool added from the template or the add-tool skill runs Python, not bash #244

Open

Description

@ooloth

Current state

Each tool added today adds bash that the Python migration will have to port, because every guide an agent follows to add a tool produces bash scripts while decision 007 says new scripts that are run are Python. The add-tool skill, the tools/@new template and tools/README.md all build install.bash, update.bash and uninstall.bash. Decision 007's own "Also update" item, saying new scripts are Python, is still unchecked. The template's install.bash and update.bash also install and upgrade the tool with brew, while the add-tool skill says a brew tool needs neither, because tools/homebrew/update.bash bundles every tool's Brewfile.

Ideal state

  • An agent following the add-tool skill or copying tools/@new produces Python for any script the new tool runs.
  • A brew tool added from the template gets no script that installs or upgrades it outside the combined Brewfile.

Decisions

Constraints

Open

Starting points

  • .claude/skills/add-tool/SKILL.md: the steps an agent follows to add a tool
  • tools/@new/install.bash: what a new tool's scripts start from today
  • docs/decisions/007-scripts-that-are-run-are-written-in-python.md: the unchecked update item

Metadata

Metadata

Assignees

No one assigned

    Labels

    maintenanceUpkeep that changes how the repo is built, not what it does

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions