spec-discover

Scan project codebases and propose spec updates under .superharness/spec/.

4|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Mrlyk/superharness --skill spec-discover-mrlyk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-discover
Source: https://github.com/Mrlyk/superharness/tree/main/skills/spec-discover
Command: npx skills add https://github.com/Mrlyk/superharness --skill spec-discover-mrlyk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help developers and AI workflows quickly understand a repository's real conventions, tooling, and architecture so that project specs stay accurate and development proceeds with consistent expectations.

Core Features & Use Cases

  • Detect project ecosystem(s) by scanning manifest and config files and load language-specific detection rules where available.
  • Perform either a full discovery when specs are empty or an incremental check comparing code changes against existing spec documents.
  • Prepare human-readable spec updates under .superharness/spec/, present findings in Chinese for confirmation, and commit changes only after user approval.
  • Fast fallback behavior for unknown ecosystems and trace logging support when an active task is present.

Quick Start

Scan the repository, detect languages, frameworks, tests, and tooling, and propose concrete updates to .superharness/spec/ for my confirmation.

Frequently Asked Questions about spec-discover

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

FAQPage Schema
How do I automatically discover project conventions and tech stack from a codebase?

To discover project conventions automatically, scan the repository to detect languages, frameworks, and tooling by reading manifest and config files, then generate proposed spec file updates under .superharness/spec/ for user confirmation.

What programming languages does project convention discovery support?

Project convention discovery supports JavaScript/TypeScript, Python, Java/Kotlin, and Swift projects by loading language-specific detection rules to identify structural patterns and tech stack configurations.

How do I check if my codebase changes conflict with existing project specs?

To check if codebase changes conflict with existing specs, perform an incremental discovery that compares recent code updates against existing spec documents in .superharness/spec/ and highlights any discrepancies for review.

Can I automatically commit project spec updates after a codebase scan?

You cannot automatically commit spec updates directly, because the scan prepares human-readable spec updates under .superharness/spec/, presents findings for confirmation, and commits changes only after explicit user approval.

What happens when scanning an unknown ecosystem for tech stack conventions?

When scanning an unknown ecosystem for tech stack conventions, the system employs a fast fallback behavior to continue processing and provides trace logging support when an active task is present.

How do I initialize project specs for a new repository from scratch?

To initialize project specs from scratch, trigger a full discovery scan when specs are empty, which detects the project ecosystem and proposes concrete structural and tooling updates to .superharness/spec/.