code-analyzer

Analyze source code to generate language-agnostic specifications and design documents.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/augentic/specify --skill code-analyzer-augentic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-analyzer
Source: https://github.com/augentic/specify/tree/main/plugins/rt/skills/code-analyzer
Command: npx skills add https://github.com/augentic/specify --skill code-analyzer-augentic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and time-consuming process of analyzing source code to generate detailed, language-agnostic specifications and design documents. It captures business logic, API contracts, and system behavior, enabling cleaner code migration and better documentation.

Core Features & Use Cases

  • Business Logic Extraction: Identifies and tags domain, infrastructure, and mechanical logic within code.
  • API Contract Generation: Documents inbound endpoints and outbound API calls with precise request/response shapes.
  • Language-Agnostic Artifacts: Produces specs.md and design.md files that are independent of the source language, suitable for any target platform.
  • Use Case: Migrating a legacy TypeScript microservice to Rust. Use this Skill to analyze the TypeScript code, generating detailed specifications that guide the Rust implementation, ensuring all business logic and external interactions are accurately translated.

Quick Start

Use the code-analyzer skill to analyze the source code located at '/path/to/source/code' and output the artifacts to '/path/to/change/directory'.

Frequently Asked Questions about code-analyzer

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

FAQPage Schema
How do I extract business logic and API contracts for code migration?

To extract business logic for code migration, you analyze source code to generate language-agnostic specification artifacts. This process identifies domain logic, infrastructure details, and API contracts, producing reconstruction-grade specifications that guide implementation in any target platform.

What is language-agnostic specification generation and when is it needed?

Language-agnostic specification generation is the process of translating source code into platform-independent design documents. It is needed when migrating legacy systems, documenting inbound endpoints, or capturing mechanical operations without tying the specifications to the original programming language.

Can I generate design documentation from source code automatically?

Yes, you can generate design documentation automatically by analyzing source code to produce language-agnostic artifacts. This includes creating detailed design.md and specs.md files that document types, constants, external services, and timing patterns without manual writing.

How do I identify and tag domain logic and infrastructure details in my codebase?

To identify and tag domain logic, you analyze the codebase to separate business rules from infrastructure and mechanical operations. This extraction categorizes specific code segments, allowing you to see precise request and response shapes for external service interactions.

Does code analysis support migrating a legacy microservice to a different language?

Yes, code analysis supports migrating a legacy microservice by generating language-agnostic specifications. By capturing the original system behavior and API contracts, these specifications ensure all business logic is accurately translated and reconstructed in the new target language.