fixScan a path with Kestrix, fix every finding at medium severity or above, and re-scan until clean or explained.
fixing-security-findingsPer-rule fix playbook for Kestrix security findings, with before and after code for every rule id (py.*, js.*, php.*, go.*, java.*, cs.*, rb.*, c.*, rust.*, swift.*, sql.*, vue.*, svelte.*, html.*, css.*, web.*, next.*, gha.*, docker.*, sh.*, tf.*, k8s.*, config.*, secret.* and dep.*). Use when a Ke
kestrix-securityRuns the local Kestrix command line tool to check things on the user's own machine and explain the result. Use when the user asks whether an email or .eml file is phishing, a scam or spoofed, whether a link or URL is safe to click, what a suspicious file, download or attachment really is, whether a
reviewSecure review of the current git diff with Kestrix, limited to changed lines.
scanRun a Kestrix security scan on a path and summarize the findings.
secure-code-reviewReviews code for security flaws with the local Kestrix scanner, fixes each finding and re-scans. Use when the user asks for a security review or to review this for security, asks "is this code safe" or "is this secure", or wants to find insecure code, check for vulnerabilities, audit or harden code.
statusShow what the Kestrix hooks did in this session: files scanned, findings reported, and files that were not security-checked, with the reason.