code-issues-find

To find security vulnerabilities and code bugs in a specific package folder, you can trigger an audit by asking the agent to analyze the target directory. The skill systematically discovers scoped issues and generates actionable ledger entries for tracking without modifying the codebase.

A ledger-based workflow for static analysis integrates findings into a centralized ledger to ensure identified code defects and risks are tracked, deduplicated, and actionable. This approach maintains a structured, non-destructive record of security vulnerabilities and contract violations for subsequent implementation.

Yes, this code review process explicitly checks for public-contract violations and compatibility breaks. It operates by analyzing code, tests, and documentation to identify these issues alongside security flaws and bugs, generating high-confidence findings that adhere to defined audit rules.

Yes, you can perform a comprehensive security audit on a newly integrated module before deployment. This ensures the module adheres to public contracts and security standards, providing a structured assessment of code defects and compatibility breaks within the scoped package.

The primary limitation of this non-destructive code issue audit is that it does not modify the codebase to fix the identified defects. It strictly generates ledger entries for subsequent implementation, meaning users must separately address the discovered bugs, security vulnerabilities, and compatibility breaks.