domains / families / software-engineering / ai-code-generation-guardrails
ai-code-generation-guardrails
authentic
Use when reviewing AI-generated code before merge or execution: plan AST/security checks, isolated behavior tests and evidence, with language-specific coverage limits.
When to use
- Review a policy for checking generated code before merging or running it.
- Define language-specific static checks, test evidence and deployment boundaries.
- Distinguish a dependency advisory scan, a linter and an AST policy check.
When not to use
- No automated checklist proves general security or finds every zero-day flaw.
- AST grammar and rule coverage depend on the actual runtime version.
- Parsing succeeds on code that can still be malicious; do not execute it to
- Reentrancy rules apply to relevant concurrent/contract code, not every Python
- This skill supplies a policy and teaching example, not a CI gate installation.
Skill page
Source