The full test suite may execute repository-controlled code and hooks
Source references: 3The Skill requires a final full-suite run. Test commands commonly load repository configuration, plugins, fixtures, and lifecycle scripts, while this instruction sets no trust boundary, exact command, network restriction, or side-effect limit.
In an untrusted or compromised repository, the test path could read available files or credentials, use the network, start services, or modify the workspace or external resources. The supplied evidence does not show that this will occur, but the instruction activates that execution path.
The source requests type checking and tests as normal verification for implementing work from a specification. No test command, hook, network operation, or suspicious script is provided, so these lines do not support the more specific claim that repository hooks will run. For an untrusted repository, the user can still require disclosure of the exact test command and its script definition before execution.
This assessment concerns the code and conditions shown, not proof that harm has occurred.Use /tdd where possible, at pre-agreed seams.Run typechecking regularly, single test files regularly, and the full test suite once at the end.Show 2 other places
---name: implementdescription: "Implement a piece of work based on a spec or set of tickets."disable-model-invocation: trueImplement the work described by the user in the spec or tickets.Use /tdd where possible, at pre-agreed seams.Run typechecking regularly, single test files regularly, and the full test suite once at the end.