Not in the top 1,000 by GitHub stars

blader/schematic

Claude Code / Codex skill: reverse engineer a product & technical spec from a git branch

History

Review weekly changes to SKILL.md before updating. Dates mark the weeks in which we observed each version; checks apply to the recorded commits.

View weekly changes

SKILL.md

Week of Nov 2, 2026 · Line counts unavailable

Before Not checked yet → After Instructions only

First observation → 297fb73e99aa

No earlier version was observed for comparison.

Compare on GitHub

View on GitHubAdd to my skills

Verified commit 297fb73e99aa4bccdb228b61252034182fdb4252

251GitHub stars
2stars in 7 days
1skill in this repository
0commits in 30 days

Heat

2.5
  • Star growth, last 7 daysNot available
  • Star growth, last 24 hoursNot available
  • Rank movement, last 7 daysNot available
  • Commits, last 30 daysNot available
  • Accounts asking about it through MCP, last 7 daysNot available
  • Hot votes this weekNot available

Heat never changes the order by stars, and sponsorship never touches it. How heat works

Stars over time

Oct 25, 2026Nov 3, 2026251

30-day change not yet available: not enough history.

Individual skills in this repository

How it works

schematic

When your agent uses it

Reverse engineer a detailed product and technical specification document from a git branch's implementation. Use when: (1) a branch has shipped or is in-progress and needs documentation, (2) you need to understand what a branch does at product and architecture level, (3) onboarding to someone else's feature branch, (4) creating PR descriptions or design docs after the fact, (5) user asks to "analyze this branch", "write a spec from the code", or "document what this branch does". Produces a structured markdown spec covering problem statement, product requirements, architecture, technical design, file inventories, testing strategy, rollout plan, and risks.

What it loads into context

Frontmatter

189 tokens

Always available to the agent

SKILL.md

2,044 tokens

When the skill is activated

Reference documents

377 tokens

Loaded on request

Token counts are estimates. Scripts run separately; they are not counted as reference context.

The playbook

  1. Problem
  2. Context / Trigger Conditions
  3. Solution
  4. Verification
  5. Example
  6. Notes

Files

  • LICENSEasset1,056 bytes
  • README.mddoc1,729 bytes
  • SKILL.mdcore8,641 bytes
  • SKILL.mdcore8,641 bytes
  • SKILL.mdcore8,641 bytes
  • SKILL.mdcore8,641 bytes
Read SKILL.md

# Reverse Engineer Spec from Branch Implementation

## Problem

Feature branches often ship without comprehensive documentation. After the fact, teams need
product specs, architectural docs, or onboarding materials that explain what was built and why.
Manually reading every file change is slow and error-prone. This skill systematically extracts
a complete spec from a branch's diff.

## Context / Trigger Conditions

- User asks to "analyze this branch" or "reverse engineer a spec"
- User asks to "document what this branch does"
- User wants a product spec, technical spec, or design doc from existing code
View the complete source on GitHub

Skills included

  • schematic

Repository facts

License
MIT
Created
Feb 15, 2026
Last pushed
Mar 11, 2026
Forks
25
Open issues
1
Project activity
Slowing

Before you install

Instructions only

Automated signals, not a guarantee

Checked Nov 6, 2026

Not fully analyzed: some files were too long, unreadable or missing. This never lowers the level.

Show 3 notes
  • SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
  • SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
  • SKILL.md:1 Analysis incomplete: Referenced executable target unavailable; not analyzed
  • No broad tool permissions
  • No dangerous shell commands
  • 2 network referencesin 1 file: README.md:18
  • No hidden or obfuscated text
  • No instruction overrides
  • No executable scripts
  • No access to secrets
  • No requests to vote in Hot
Show all 2 signals by file

README.md

  • Network accessline 18
    git clone https://github.com/blader/schematic.git ~/.claude/skills/schematic
  • Network accessline 26
    git clone https://github.com/blader/schematic.git ~/.codex/skills/schematic

How the signals fit together

Facts from a static read of the files at the pinned commit. They describe what the code does, not why.

Signal confidence: 2 facts
  • Network access in code of documentationREADME.md:18Low confidence
  • Network access in code of documentationREADME.md:26Low confidence

Works with

Agent compatibility, from the files in this repository
AgentStatusEvidenceInstall to
Claude CodeCompatibleStandard SKILL.md SKILL.md.claude/skills/<skill-name>/
CodexCompatibleStandard SKILL.md SKILL.md.agents/skills/<skill-name>/
CursorCompatibleStandard SKILL.md SKILL.md.cursor/skills/<skill-name>/
Gemini CLICompatibleStandard SKILL.md SKILL.md.gemini/skills/<skill-name>/
GitHub CopilotCompatibleStandard SKILL.md SKILL.md.github/skills/<skill-name>/
OpenCodeCompatibleStandard SKILL.md SKILL.md.opencode/skills/<skill-name>/
  • Native The repository ships a manifest, folder or frontmatter field for this agent.
  • Compatible A standard SKILL.md that this agent can read.
  • Unknown No evidence either way.

Derived automatically from paths, manifests and frontmatter. Not tested on each agent.