CLI Reference

strictacode analyze

Analyzes a codebase and generates a quality report.

strictacode analyze PATH [OPTIONS]

Arguments

Argument	Description
PATH	Absolute path to the project directory to analyze

Options

Option	Default	Description
--short	false	Show only project summary, skip packages/modules
--details	false	Include class, method, and function details
-f, --format	text	Output format: text or json
--top-packages	from config	Number of top packages to show
--top-modules	from config	Number of top modules to show
--top-classes	from config	Number of top classes to show
--top-methods	from config	Number of top methods to show
--top-functions	from config	Number of top functions to show
-o, --output	—	Save output to a file instead of stdout
--threshold	—	Fail if any metric exceeds the given threshold

Thresholds

The --threshold option enables quality gates. The command exits with code 1 if any specified metric exceeds its threshold.

Single value (applies to Project Score only):

strictacode analyze . --threshold 60

Multiple metrics (key=value, comma-separated):

strictacode analyze . --threshold score=60,rp=70,op=50,density=40

Available keys:

Key	Metric	Type
score	Project Score	int
imb	RP/OP Imbalance	int
rp	Refactoring Pressure	int
op	Overengineering Pressure	int
density	Complexity Density	float

When a threshold is exceeded, the command prints an error and exits with code 1. All checks are performed — multiple thresholds can fail in a single run.

Output Formats

Text (default):

strictacode analyze ./src
strictacode analyze ./src --short
strictacode analyze ./src --details

• --short — project-level summary only
• default — project + top packages + top modules
• --details — includes classes, methods, and functions

JSON:

strictacode analyze ./src --format json

Structured JSON with full metrics hierarchy. Suitable for CI/CD pipelines and programmatic processing.

Saving Output to File

Use -o / --output to save the report to a file:

strictacode analyze . --format json --output baseline.json
strictacode analyze . --output report.txt

The saved JSON file can be used as input for the compare command.

Error Handling

The command exits with an error if: - The path does not exist - The path is not a directory - The language cannot be detected

strictacode install agent-skill

Installs strictacode as a skill for AI coding assistants.

strictacode install agent-skill --agent AGENT [--name NAME]

Options

Option	Default	Description
--agent	(required)	Target agent platform
--name	strictacode	Custom skill name

Supported Agents

Agent	Skill Path
claude	~/.claude/skills/{name}/SKILL.md
cursor	~/.agents/skills/{name}/SKILL.md
codex	~/.codex/skills/{name}/SKILL.md
gemini	~/.agents/skills/{name}/SKILL.md
antigravity	~/.agents/skills/{name}/SKILL.md

Example

strictacode install agent-skill --agent claude

strictacode compare

Compares two analysis results (JSON files) and shows the diff between their metrics.

strictacode compare BASELINE CURRENT [OPTIONS]

Arguments

Argument	Description
BASELINE	Path to the baseline JSON analysis result
CURRENT	Path to the current JSON analysis result

Options

Option	Default	Description
-f, --format	text	Output format: text or json
--details	off	Include full results for both baseline and current
-o, --output	—	Write output to file instead of stdout
--threshold	—	Fail if the diff exceeds the given threshold

Thresholds in Compare

When --threshold is specified, the command checks whether the difference between the two results exceeds the threshold. This is useful for CI/CD quality gates that block PRs if metrics degrade beyond an acceptable limit.

strictacode compare baseline.json current.json --threshold score=10,rp=5

The threshold syntax is the same as in analyze — see Thresholds.

Example

# Save baseline on main
strictacode analyze . --format json --output baseline.json

# After changes, save current state
strictacode analyze . --format json --output current.json

# Compare
strictacode compare baseline.json current.json

Output:

Diff:
  * score: 7
  * complexity_density: 1.7
  * refactoring_pressure: 7
  * overengineering_pressure: 2

With --details:

Diff:
  * score: 7
  * complexity_density: 1.7
  * refactoring_pressure: 7
  * overengineering_pressure: 2

---

Baseline:
  * score: 35
  * complexity_density: 12.4
  * refactoring_pressure: 55
  * overengineering_pressure: 20

---

Current:
  * score: 42
  * complexity_density: 14.1
  * refactoring_pressure: 62
  * overengineering_pressure: 22

Configuration File Loading

strictacode looks for a configuration file in the root of the analyzed project. Priority order:

1. .strictacode.yml
2. .strictacode.yaml
3. .strictacode.json

See Configuration for available options.