Build
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent build automation skill, but it can edit your repository, run local project commands, and commit changes, so use it only in trusted workspaces.
This skill appears purpose-aligned for executing an existing implementation plan. Before using it, make sure the repository, plan.md, docs/workflow.md, hook configuration, package scripts, and Makefile targets are trusted, because the skill may run commands, edit files, and commit changes automatically.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked in a project, the agent may change source files, update plan files, run commands, and commit changes to local git history.
The skill explicitly gives the agent shell execution and file-editing tools and directs it to update files and create commits.
allowed-tools: Read, Grep, Bash, Glob, Write, Edit... Execute tasks... implements it with TDD workflow, commits, and updates progress.
Use this only in repositories where you trust the plan files and project scripts, and review diffs and commits before relying on the result.
Project-defined setup or hook commands could run code from the repository as part of the build workflow.
These are disclosed, purpose-aligned setup steps, but they can execute local project tooling or package scripts before the first commit.
If not active — install before first commit: husky: `pnpm prepare` (or `npm run prepare`); pre-commit: `uv run pre-commit install`; lefthook: `lefthook install`
Review hook configuration, package scripts, and Makefile targets in unfamiliar repositories before allowing the skill to run setup or test commands.
Old or cross-project context could influence current code changes, and private project information may be surfaced into the agent context if those MCP tools are enabled.
The skill may use retrieved prior-session, cross-project, and persistent progress context to guide implementation.
`session_search(query)` — find how similar problems were solved before; `project_code_search(query, project)` — find reusable code across projects; `.solo/pipelines/progress.md`... Use this to avoid repeating completed work.
Ensure the MCP search indexes and progress files contain only projects and history you are comfortable reusing for this build task.