skills.rest
rabbicse
rabbicseCOMMUNITY
Explore all skills by this author →
GitHub

spec-miner

Extract EARS-formatted specifications from source code with evidence and code locations.

2|Updated Apr 18, 2021
Search Tags:#architecture analysis#legacy code#reverse engineering#specification extraction#code archaeology#ears requirements
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill spec-miner-rabbicse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-miner
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/spec-miner
Command: npx skills add https://github.com/rabbicse/go-projects --skill spec-miner-rabbicse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Spec Miner helps you understand undocumented or inherited codebases by turning implementation details into structured, evidence-based specifications.

Core Features & Use Cases

  • Reverse Engineering: Trace how a system works from source code, configuration, and file structure.
  • Specification Extraction: Convert observed behavior into EARS-style requirements with code references.
  • Architecture and QA Review: Document data flows, security patterns, error handling, and open questions for legacy projects.
  • Use Case: Use it when onboarding to an old repository, preparing feature documentation, or auditing a system that has little or no existing docs.

Quick Start

Use the spec-miner skill to analyze this codebase and produce a reverse-engineered specification with evidence, uncertainties, and recommendations.

Frequently Asked Questions about spec-miner

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

FAQPage Schema
How do I extract specifications and business logic from a legacy codebase?▼

Reverse engineering undocumented code involves tracing dependencies, routes, and business logic from source files to generate structured specifications with code references and uncertainty analysis.

What is the best way to document an inherited system with no existing docs?▼

Documenting an inherited system requires thorough source exploration to map architecture, data flows, and security patterns into structured EARS-style requirements with explicit error-handling analysis.

How do I generate EARS requirements from source code?▼

Generate EARS requirements from source code by tracing observed behavior and implementation details, then converting them into evidence-based specifications that include code locations for observations.

Can I use code archaeology to audit security and error handling in an old repository?▼

Code archaeology audits security and error handling by mapping implementation details from the old repository, documenting security patterns, and explicitly analyzing error-handling mechanisms and open questions.

Does reverse engineering a legacy system require analyzing code dependencies and routes?▼

Reverse engineering a legacy system requires analyzing code dependencies and routes to accurately trace system architecture and map business logic into evidence-based documentation.

Related Skills

Explore More Software Engineering Skills→
i3ringiti3ringit
3

git-history-analyzer

Analyze git history to trace file evolution, contributors, and change patterns.

Community
Intermediate
JeffallanJeffallan
10.9k

spec-miner

Extract undocumented functionality from codebases into EARS-formatted specifications.

Community
Advanced
macaughmacaugh
5

Static Vulnerability Analysis

Detects injection, memory safety and authorization flaws in multiple languages.

Community
Advanced
luongnv89luongnv89
40.9k

api-documentation-generator

Generate API documentation from source code into Markdown and OpenAPI-style specs.

Community
Basic