Skip to main content

Overview

Understanding an existing codebase — for an audit, due diligence, a modernization push, or a system you inherited — traditionally requires months of manual analysis. Zenable provides automated deep-dive analysis that maps dependencies, identifies risks, and creates implementation roadmaps - giving you complete understanding of your code in hours, not months.

The Zenable Assessment skill

The assessment skill is a guided, interview-driven assessment for Claude Code. It ships in the z plugin and runs in five phases:
  1. Frame and define. The skill asks who the report is for, why it exists, how deep to go, and what is in scope, then hands off to the z:setup skill, which mines the standards your repository already has written down (ADRs, rules files, linter config) into candidate requirements, triages them with you, and persists the survivors as scoped Zenable requirements through the MCP server.
  2. Evaluate. It runs zenable check and an AI review pass against those same requirements, then merges and deduplicates the two.
  3. Report. It populates an HTML report template, walks you through it, and rebuilds as you iterate.
  4. Verify (opt in). It audits every factual claim in the report adversarially and fixes or removes what does not hold.
  5. Groom. A short interview on the report’s shape, severity calibration and emphasis with the person who has to stand behind it.

Prerequisites

  • The Zenable CLI, signed in with zenable login
  • Claude Code with the Zenable MCP server installed and authenticated (zenable install mcp claude-code --project, then /mcp)
  • A Zenable account that can create scopes and requirements

Install and run

Inside Claude Code:
Confirm the workspace location when asked. By default it is ./zenable-assessment/<timestamp>/ inside the repository; add it to .gitignore. Everything under its context/ directory is source material kept unchanged, and everything under evidence/ is generated by a tool and never edited by hand.

What it produces

  • Scopes and requirements in your tenant, created at beta, that your hooks, pre-commit checks and pull request reviews enforce from then on
  • evidence/findings/ with the zenable check JSON and SARIF, the AI pass, and the merged set
  • dist/report.html, a self-contained report where every finding names the file, the line and the requirement it violates
  • dist/assessment-bundle.zip, the report with its context, evidence and experiments
Upload the bundle on the Assessments page of the Zenable app (100 MiB limit). The report renders in a sandboxed frame, and links to files in the bundle fetch through your normal session. The same bundle also opens from disk.
The skill produces text an LLM wrote. The verify phase exists for reports that go to an auditor or a customer: run it before you share one outside your team.

Out-of-the-Box Analysis

Zenable automatically detects these code issues:

Standard Code Assessment Checks

  • Code Smells - Deep nesting, long methods, duplicate code
  • Outdated Patterns - Deprecated APIs, obsolete libraries
  • Security Vulnerabilities - SQL injection, hardcoded secrets, weak crypto
  • Technical Debt - Missing tests, poor documentation, cyclomatic complexity
  • Dead Code - Unused functions, unreachable code
  • Performance Issues - N+1 queries, inefficient algorithms

Custom Organization Requirements

Apply your specific modernization criteria:
“All of our services must be migrated to our new microservices architecture, use our internal authentication service, follow our naming conventions, and include telemetry with our monitoring stack.”

In Action

Custom Modernization Examples

Example: Microservices Migration

Your Policy: “All monolithic components must be refactored into domain-bounded microservices”

Example: Internal Standards Migration

Your Policy: “Replace all direct database calls with our DataAccess layer”

Example: Tech Stack Modernization

Your Policy: “Migrate from jQuery to React, replace callback patterns with async/await”

Example: Observability Requirements

Your Policy: “All services must add distributed tracing and structured logging”

Benefits

  • Complete Tech Debt Understanding - Know exactly what needs modernization
  • Custom Migration Path - Enforce your specific architectural standards
  • Risk-Based Prioritization - Focus on critical issues first
  • Accelerated Modernization - Move from months to hours of analysis