python-arch-optimizer
PassAudited by ClawScan on May 1, 2026.
Overview
This skill is a coherent Python project restructuring helper, but users should review the migration plan because it can move and create project files.
This appears safe for its intended use, but treat migration as a real file-changing operation: run the dry-run mode first, review the generated plan, confirm the target path, and keep a backup or clean Git state before applying changes.
Findings (2)
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 run on the wrong directory or without reviewing the plan, project files could be rearranged or temporarily deleted during rollback handling.
The migration script can move files, create files, and delete/restore the selected project directory during rollback. This is disclosed and purpose-aligned, but it is real local mutation authority.
shutil.move(str(src), str(tgt)) ... p.write_text(content, encoding="utf-8") ... shutil.rmtree(self.project)
Run `--dry-run` first, save/review the plan, ensure the project is under version control or separately backed up, and only confirm migration for the intended project root.
If the user later installs and runs pre-commit, third-party hook code may run in the project environment.
The generated pre-commit configuration references third-party GitHub hook repositories. They are pinned and expected for a Python engineering template, and the skill does not execute them automatically.
repo: https://github.com/pre-commit/pre-commit-hooks
rev: v4.5.0Review generated `.pre-commit-config.yaml` entries and pinned revisions before running `pre-commit install` or using the hooks.