timewarp

Included with Lifetime

$97 forever

Use to reconstruct application/codebase state at a past commit, branch, or moment. "What did this look like 3 weeks ago", "go back to before the auth refactor". Read-only — uses git worktree to avoid disturbing current work.

Code Review

What this skill does


# timewarp

State reconstruction debugging. Walk back to a past state cleanly via git worktree. Investigate without polluting current work.

## Method

1. **Pin the moment.** User specifies one of:
   - SHA: `git checkout <sha>`
   - Date: `git rev-list -n1 --before="<date>" main`
   - Tag/branch: `<ref>`
   - "Before X": `git log -S "<symbol>" --before` to find when X was introduced
2. **Worktree.** `git worktree add ../timewarp-<ref> <ref>`. Never check out in-place — that disturbs current state.
3. **Reproduce build.** `cd` to worktree; `npm install` (or equivalent). Note: deps may be older.
4. **Investigate.** What's the question? Run, query, read files in the worktree.
5. **Compare** (optional). Diff between worktree and current to highlight what changed.
6. **Cleanup.** `git worktree remove ../timewarp-<ref>` when done.

## Output shape

```
Anchored at:    <ref> (<sha7>, <date>)
Worktree:       <path>

Reproduction:
  Build:        <command>
  Status:       ✓ green | ✗ <error>

Findings:
  <answers to user's question, w/ file:line citations from past state>

Diff vs current (if requested):
  <key differences>

Cleanup:        <command>
```

## Rules

- **Always use a worktree.** Never check out a past ref in the active workspace.
- **Note dep drift.** Old code may have old deps; install may differ.
- **Read-only investigation.** Do not modify the past worktree as if it were current.
- **Cleanup is mandatory.** Don't leave worktrees lingering.
- Memory captures the timewarp result so it's reusable.

## Anti-patterns

- `git checkout <sha>` in the main worktree (loses current state if uncommitted)
- Modifying the historical worktree expecting it to merge back
- Not running `npm install` and getting confused by missing modules
- Forgetting cleanup; worktrees pile up

## When NOT to use

- "Show me the diff" — `git diff` directly
- Restoring deleted code — `/siftcoder:zen` undo via git, not timewarp
- Performance over time — needs benchmarking framework, not just reconstruction

## Subagent dispatch

- `Explore` inside the worktree once it's created
- `Bash` for the worktree management
- `Agent` with `isolation: "worktree"` is a natural fit if you want a sub-agent to do the timewarp investigation

## Value over native CC

CC will run git commands. CC won't naturally enforce worktree-isolation discipline, install deps, and clean up afterwards. The discipline keeps current work safe.

Files: 1

Size: 2.6 KB

Complexity: 7/100

Category: Code Review

Source: https://github.com/ialameh/sift-coder/tree/main/skills/quality/timewarp

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts