Updated 1d ago
by theonly1me
shadowclone
Your engineering taste, in every coding agent. Shadowclone learns your rules and delivers them as skills to Claude Code, Codex, Cursor, Pi, and Antigravity, and as a GitHub cloud bot.
21 GitHub stars (21)
| Period | New stars |
|---|---|
| Oct 15 | 0 |
| Oct 16 | +1 |
- 16 skills (16 skills found in its SKILL.md files)
- 0 forks (0 forks)
- 1d ago last update (Last updated 1d ago)
Install
Skills CLI
npx skills add theonly1me/shadowclone
Asks which skills and agents to install. Just one: npx skills add theonly1me/shadowclone --skill choose-by-consequence — add -g for every project.
Claude Code
git clone https://github.com/theonly1me/shadowclonecp -r "shadowclone/skills/choose-by-consequence" ~/.claude/skills/
Copies the choose-by-consequence skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.
Plugin
/plugin marketplace add theonly1me/shadowclone
Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.
Skills can run code on your machine — read the SKILL.md first.
What it does
In the author's own words, from each skill's SKILL.md — showing the first 16 of 46 files.
-
choose-by-consequence
Use when code must decide what happens on an unusual or failing path. Also use it when the user says "just handle that case", "skip it if it fails", or "is this the best way?". Compares the easy route with each alternative by what it does to the user's files, data, and output. Picks the option that fails loudly and keeps every count and exit code true. Never writes through a file that the change…
skills/choose-by-consequence/SKILL.md on GitHub (opens in a new tab) -
design-deep-modules
Use when designing or reshaping a module, or when callers coordinate too many steps. Also use it when the user says "this is hard to test", "callers know too much", or "simplify this interface". Puts related state and decisions behind a small interface that states what the caller wants. Tests then use that interface instead of the internal steps. Not for typing values at a boundary (use `typescri…
skills/design-deep-modules/SKILL.md on GitHub (opens in a new tab) -
diagnose-before-editing
Use when behavior fails, flakes, or slows down, and nobody knows the cause yet. Also use it when the user says "why does this fail?", "it worked yesterday", or "this got slow". Reproduces the failure, makes it smaller, and tests one cause at a time until one cause predicts the symptom. Then fixes the cause at its origin, not the symptom. Not for scoping a fix whose cause you already know (use `sc…
skills/diagnose-before-editing/SKILL.md on GitHub (opens in a new tab) -
guided-pr-review
Use when the user says "guide me through this PR" or "review PRs 1, 2, 3". Reuses shadowclone-review locally and builds a standalone HTML with actual diffs, behavior traces, and selection comments. Saves notes into the same file. Not for fixing reviewed code (use `shadowclone-work`).
skills/guided-pr-review/SKILL.md on GitHub (opens in a new tab) -
plan-with-review-page
Use before a change that touches many files, needs many steps, or has open design choices. Also use it when the user says "plan this first", "what is your approach?", or "do not code yet". Explores the code read-only, asks one round of decisions with the recommended option first, and writes one plan. Builds a self-contained HTML review page from a template, and checks the page with a validator. N…
skills/plan-with-review-page/SKILL.md on GitHub (opens in a new tab) -
research-primary-sources
Use when a decision depends on how a library, platform, protocol, or tool behaves, and that behavior can change by version. Also use it when the user says "check the docs", "is this still true?", or "what does the spec say?". Finds the first-party source for the installed version and reads it. Separates what the source guarantees from what you infer. Not for debugging a failure in your own code (…
skills/research-primary-sources/SKILL.md on GitHub (opens in a new tab) -
resolve-conflicts-by-intent
Use when Git reports conflicts during a merge, a rebase, or a cherry-pick. Also use it when the user says "fix the merge conflicts", "rebase onto main", or "the merge broke the build". Traces each side of a conflict to the change that it came from. Keeps both intents when they fit together, and asks when they do not. Then runs the checks on the combined result. Not for choosing what a new behavio…
skills/resolve-conflicts-by-intent/SKILL.md on GitHub (opens in a new tab) -
scope-confirmed-changes
Use when fixing a bug, a regression, or a confirmed review finding. Also use it when the user says "fix this bug", "it is broken", or "keep the change small". Reproduces the issue before any fix, with a test, a real command, or the real interface. After the fix, the same reproduction must pass. Keeps the change to confirmed, reachable behavior. Not for checking review comments before a fix (use `…
skills/scope-confirmed-changes/SKILL.md on GitHub (opens in a new tab) -
shadowclone-review
Use when the user asks for a review of a pull request, or when a review packet from `shadowclone review` arrives. Also use it when the user says "review PR 123", "find bugs in this pull request", or "is this PR safe to merge?". Runs a strict adversarial review for correctness, security, performance, reliability, and compatibility. Each claim quotes its evidence, a fresh refuter tests each finding…
skills/shadowclone-review/SKILL.md on GitHub (opens in a new tab) -
shadowclone-work
Use when the user asks to implement a change and open a pull request, or to get a pull request ready to merge. Also use it when the user says "fix the red PR", "address the review comments", or "restack my PRs". Covers CI failures and flakes, bot and human review threads, conflicts with a moving base, and stack restacks. Takes the work to a pull request that is ready for review, and keeps it ther…
skills/shadowclone-work/SKILL.md on GitHub (opens in a new tab) -
tests-that-catch-bugs
Use when adding, changing, or reviewing tests. Also use it when the user says "add a regression test", "write the test first", or "make sure this cannot break again". Writes a few tests that each name a bug and check the result where the user sees it. Expected values come from an independent source, and each test fails without the change. Test first is an ordering choice inside this skill. Not fo…
skills/tests-that-catch-bugs/SKILL.md on GitHub (opens in a new tab) -
typescript-type-safety
Use when changing TypeScript types, parsing input that enters typed code, or removing unsafe casts. Also use it when the user says "fix the types", "remove the as casts", or "make invalid states impossible". Models each valid state with types, so that invalid combinations fail to compile. Checks outside input with a type guard or a schema instead of an assertion. Not for designing module boundari…
skills/typescript-type-safety/SKILL.md on GitHub (opens in a new tab) -
verify-and-review
Use before you say that work is done, fixed, or ready for review. Also use it when the user says "make sure it works", "verify this", or "is it ready?". Runs the command or page that the user will use, and reads every count, status line, and exit code. Reviews the whole diff, and labels each claim as measured, inferred, or not verified. This catches a wrong count or a buried warning before handof…
skills/verify-and-review/SKILL.md on GitHub (opens in a new tab) -
verify-review-findings
Use when a pull request has review comments or bot findings to check. Also use it when the user says "are these comments right?", "triage the review", or "check what the bot found". Checks each finding against the code at the head of the pull request, and confirms the file, the line, and the claim. Asks what each suggested fix would break, reports a verdict for each finding, and waits. Not for wr…
skills/verify-review-findings/SKILL.md on GitHub (opens in a new tab) -
write-plain-english
Use when writing or editing prose that people read, such as documents, pull requests, commit messages, review comments, chat replies, or skills. Also use it when the user says "make this clearer", "simplify the wording", or "this is a wall of text". Rewrites the text in plain technical English, with one idea in each sentence and no dashes. Then runs a checker that reports long sentences and dashe…
skills/write-plain-english/SKILL.md on GitHub (opens in a new tab) -
shadowclone-build-preferences
Read before acting for the selected working preferences.
.agents/skills/shadowclone-build-preferences/SKILL.md on GitHub (opens in a new tab)
No skill matches that filter.
Review before you install
A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.