warden-skill

Automated security analysis on pull requests is triggered by configuring event-driven rules. You can configure the skill to run a security review on specific directories and automatically fail the build if critical vulnerabilities are detected.

Static code analysis on local commits is supported through event-driven triggers. You can run the warden skill to analyze all uncommitted changes or target specific file paths within your current git repository.

Custom triggers for code analysis are configured via a warden.toml file. This configuration file allows you to define specific rules for when and where analysis executes across your git-based workflows.

Warden CLI integration is required to execute automated code analysis and reporting. The CLI operates the underlying skills that produce structured findings with severity levels for your code changes.

Automatically applying suggested fixes from code analysis is supported by the reporting feature. The structured findings include severity levels and allow auto-applying fixes to resolve detected bugs and style issues.

Event-driven code analysis is an automated process that triggers on repository changes like pull requests or local commits. It executes configurable skills to produce structured reports with findings, ensuring consistent codebase quality.