GitHub collection
theonly1me/shadowclone
Imported from GitHub — is this yours?
46 skills imported from this repository.
- Stars
- 26
- Forks
- 2
- License
- MIT
Skills (46)
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. Pi
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
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 sy
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,
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
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 fi
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 reproduc
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, se
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, conflic
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
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
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
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 tec
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. Pi
data-handling
Read before changing capture, indexing, redaction, learning, skill publication, engine execution, Actions bot setup, or any path that stores or sends user data.
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
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 sy
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,
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
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 fi
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 reproduc
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, se
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, conflic
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
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
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
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 tec
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. Pi
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
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 sy
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-wor
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", "make a plan", "think this through", or "do not code yet". Explores the code read-only, asks the open decisions with the recommended option
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
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 fi
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 reproduc
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, se
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, conflic
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
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
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
verify-review-findings
Use when a pull request has review comments or bot findings to check or address. Also use it for "are these comments right?", "triage the review", "address the review comments", "check the PR comments", or "check what the bot found". Checks each finding against the code at the he
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 tec
setup-clones
Configure shadowclone clones on this machine. A clone is Claude Code or Codex that works as the user, in Docker, toward a draft pull request. Use it when the user asks for clones, cloud sessions, or a background agent that works as them.
setup-shadowclone
Install and configure shadowclone for the user from start to finish. Use it when the user asks to "set up", install, configure, or start shadowclone with Claude Code, Codex, Cursor, Pi, Antigravity, OpenCode, or another agent.
MCP servers (3)
-
shadowclone
stdio
bun -
shadowclone
stdio
shadowclone -
shadowclone
stdio
shadowclone
Connection details are shown as declared in the repository; arguments and environment values are deliberately not imported.