Code Formatting
Warn
Audited by Runlayer on Feb 22, 2026
Risk Level: MEDIUM
Scan Summary
Flagged Files (1)
SKILL.mdHIGH
78.3%
Malicious tool definition detected
These are non-negotiable HyperShift requirements." --- # Code Quality, Formatting and Conventions ## Code Formatting and Linting - **Use `make lint-fix`** after writing Go code to automatically fix most linting issues - **Run `make verify`** to verify both linting and tests pass before committing - **For markdown files**, use `make verify-codespell` to catch spelling errors ## Test Conventions - MANDATORY **NON-NEGOTIABLE RULE**: Every Go test name MUST follow this exact format: ```go name: "Whe
Audit Metadata