tama find-violations

Replays the real shared pre-write hook against files in one or more repositories and reports the first content-rule violation per file without modifying the repositories.

#Invocation

tama find-violations (--repo <path> | --tree <dir> | --owner <gh-user-or-org> | --me) [...]
                     [--json] [--hook <path>] [--clone-dir <dir>]

Targets are repeatable and combinable. --repo names one directory; --tree discovers Git checkouts; --owner uses gh and shallow-clones missing repositories; --me selects the authenticated user and their organizations. --hook overrides the replayed hook, --clone-dir changes the clone cache, and --json selects structured reports.

#Output and state

Text mode groups findings by rule and ends with repository, violation, and discovery-problem totals. JSON returns repos, problems, and totals. Exit 0 means no violations or problems; any violation or discovery problem exits 1. Command-gating rules are out of scope because they inspect shell commands rather than file content.

#Refusals and failures

Missing targets, empty or missing option values, and unknown arguments print usage and exit 2. Missing paths produce exactly hook not found: <path>, repo not found: <path>, or tree not found: <path> and exit 2. When discovery yields no repositories, Tama writes no repositories found; it exits 1 if discovery also reported a problem, otherwise 0.

Return to the complete CLI command tree.