Menu
Discover and run this project's `./repo` commands (build, test, format, lint, etc.) via the `repo_run` MCP tool instead of invoking the CLI through Bash.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Resolve an uncertainty during spec authoring by running a throwaway investigation and recording a concluded docs/spike/SPIKE-<n>.md evidence artifact. Use when a spec or ADR makes a design claim that is not yet backed by a concluded spike, a cited code path, or a doc — the spec gate rejects uncited claims and open questions.
Publish pending changes in tools/framework/ to the repokit upstream repo. Handles branch switch, testing, versioning, push, and submodule pin.
| name | repo-tools |
| description | Discover and run this project's `./repo` commands (build, test, format, lint, etc.) via the `repo_run` MCP tool instead of invoking the CLI through Bash. |
The repokit framework exposes each project tool as a ./repo <name>
subcommand. The exact set of registered commands is project-defined and
discoverable at runtime.
Run ./repo --help (Bash) to enumerate the commands registered in the
current project. Common command names you should expect to see:
build — compile / build the projecttest — run the test suitetest-cov — run tests with coverageformat — apply code formatterslint — run lintersclean — remove build artifactsOther commands may exist depending on the project's config.yaml. Always
check ./repo --help instead of assuming.
The agent has access to a repo_run MCP tool that targets the correct
working directory (main workspace or worktree) automatically. Prefer it
over invoking ./repo via Bash — repo_run produces structured output,
auto-logs to _build/logs/, and avoids quoting / shim issues on Windows.
Example: repo_run(command="test") runs the project's test suite.