investigating

Included with Lifetime

$97 forever

Create and run a Crabshell I investigation document from Codex. Use for evidence-heavy research that needs multiple source types, cross-review, and documented conclusions; not for quick questions.

Code Review

What this skill does


# Investigating

Use this when a question needs a durable investigation record, not just a chat answer.

## Create The I Document First

Run:

```bash
node scripts/codex-docs.js investigation "topic" --topic="what is being investigated and why" --questions="Q1; Q2; Q3" --sources="Internet: TBD; Local: TBD; User-specified: TBD" --constraints="[Project] ...; [Inferred] ..."
```

The script creates `.crabshell/investigation/INNN-*.md` and appends to `.crabshell/investigation/INDEX.md`.

## Investigation Workflow

1. Read the new I document before researching.
2. Use at least two source types unless the user explicitly restricts scope:
   - Internet or external documentation when current/public facts matter.
   - Local files, code, tests, configs, or logs when project behavior matters.
   - User-provided URLs/files when supplied.
3. Fill `## Investigation Log` with separate workstreams. Each workstream needs evidence: commands, file paths, URLs, dates, or direct observations.
4. Fill `## Cross-Review` before synthesis. Challenge the workstreams for contradictions, missing sources, stale facts, and weak evidence.
5. Fill `## Synthesis` and `## Conclusions` in the document before summarizing in chat.
6. In `## Conclusions`, answer each question individually, include confidence level, and list remaining gaps.

The document update is the primary output. The chat response should be a short summary pointing to the I document.

Files: 1

Size: 1.6 KB

Complexity: 5/100

Category: Code Review

Source: https://github.com/zipperbagcoffee/crabshell/tree/main/codex-skills/investigating

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