kantra-analyze

Analyze application source code for violations using Kantra CLI.

Updated Oct 28, 2025
One-click install
npx skills add https://github.com/JonahSussman/project-eris --skill kantra-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kantra-analyze
Source: https://github.com/JonahSussman/project-eris/tree/main/.claude/skills/kantra-analyze
Command: npx skills add https://github.com/JonahSussman/project-eris --skill kantra-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill orchestrates Kantra to analyze application source code for violations, helping you find issues early and reduce code quality risk.

Core Features & Use Cases

  • Unified analysis: Run Kantra's analyze to detect violations across projects.
  • Targeted filtering: Narrow input and focus on relevant code paths to avoid noise.
  • Output interpretation: Filter and format the YAML output to surface actionable incidents.

Quick Start

Run the kantra analyze with your source directory and examine output.yaml for violations.

Frequently Asked Questions about kantra-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify code violations in my application using static analysis?

Static analysis scans source code for violations without executing it. Kantra's analyze command detects issues across your codebase by examining patterns against a ruleset. Point it to your source directory and specify target technologies to filter relevant violations for your stack.

Can I run code violation analysis with Kantra on a specific directory?

Yes. Kantra analyze accepts an input directory flag to target specific source paths. Specify your application code directory (typically under /src/) and provide target technologies to focus the scan and reduce noise from unrelated code.

What output format does Kantra analysis produce?

Kantra analyze outputs results in YAML format ready for extraction and interpretation. The output file contains filtered violations matching your specified targets, making it easy to parse and act on findings programmatically.

Do I need prior setup before running Kantra analysis?

Kantra integration must be present in your project. The analyze command requires your source directory path and target technology specifications. PyYAML dependency handles output formatting, and the Skill handles scanning and filtering automatically.

How does Kantra filtering reduce analysis noise?

Kantra analyze filters violations by target technologies you specify, focusing only on relevant code paths and frameworks. This narrows results to actionable incidents matching your stack, avoiding generic warnings that don't apply to your application.