Leaderboard/Product/schematic
Last commit on March 11, 2026·Created on February 15, 2026

blader/schematic

Turns a branch's implementation into a spec the team can use.
Combined rank
#669
across all skills
In Product
#14
category rank
Stars
238
+0.4% in last 7d
Forks
25
0.0% in last 7d
Watchers
2
0.0% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

This skill systematically reverse-engineers a git branch's changes into a structured product and technical specification document. It scopes the diff, explores changed files in parallel, cross-checks for gaps, and produces a markdown spec covering problem statement, architecture, testing strategy, and rollout. It helps engineering managers, code reviewers, documentation specialists, and onboarding leads turn code changes into clear, auditable documentation without reading every file manually.

WHO IT'S FOR
Feature Branch Owners
document implemented features after the fact
Pull Request Reviewers
understand branch scope and architecture quickly
Onboarding Engineers
learn unfamiliar feature branches efficiently
Engineering Managers
track feature progress through systematic doc
Repository contents

1 skill file

Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill

Follow the documented setup, then try a first task.

I’m using

Claude Code via Git

Installs: Installs the schematic skill repository for Claude Code. · Claude Code

Before you start
  • Claude Code installed
  • Git installed
  1. Run this command in a terminal to clone the repository into Claude Code's skills directory.

    git clone https://github.com/blader/schematic.git ~/.claude/skills/schematic
  2. Restart Claude Code so it discovers the skill.

SKILL.md · Checked Sep 18, 2026README.md · Checked Sep 18, 2026

Give it something to do.

Suggested first task

Reverse-engineer a branch specification

Uses schematic

  • A Git repository with the target branch checked out
  • The base branch name to substitute for <base-branch>
Use the schematic skill to reverse engineer a structured product and technical specification from the currently checked-out branch, comparing it with <base-branch>. Replace <base-branch> with the branch that this work branched from.
SKILL.md · Checked Sep 18, 2026README.md · Checked Sep 18, 2026