learn

Included with Lifetime

$97 forever

Save a reusable pattern from this session to the knowledge base. Use for /learn, "remember this", "save this pattern". NOT for session state (/save-session) or full session review (/introspect).

Code Review

What this skill does


# Learn: Save an Operational Instinct

**EXECUTE this skill now.** Follow the workflow steps below using the provided $ARGUMENTS. Do NOT describe, summarize, or explain this skill — run it.

## Constants

- `INSTINCTS_DIR`: `C:/Users/gurusharan.gupta/Agents/Claude Code/instincts`

## Arguments

`$ARGUMENTS` — optional description of the pattern to save. If empty, infer it from recent conversation context.

---

## Workflow

### Step 1: Identify the Pattern

If `$ARGUMENTS` is provided, use it as the pattern description.

Otherwise, infer from session context:
- What non-obvious technique was just used?
- What error was resolved in a way worth remembering?
- What approach was validated and should be repeated?

**Only save instincts that are:**
- Non-obvious (not derivable from docs in 30 seconds)
- Reusable (applies beyond this specific project)
- Validated (it worked — not a hypothesis)

Skip if the pattern is trivial, project-specific, or already covered by a golden principle.

### Step 2: Classify the Instinct

Assign:

- **domain** (pick one): `context-management` | `skill-design` | `model-routing` | `debugging` | `testing` | `security` | `git` | `tooling` | `api` | `general`
- **confidence** (0.3–0.9):
  - 0.3–0.5: Worked once, uncertain if general
  - 0.6–0.7: Worked 2–3 times, likely general
  - 0.8–0.9: Confirmed across multiple contexts
- **trigger**: One-line description of when to apply this instinct

### Step 3: Check for Duplicates

```bash
ls ~/Agents/Claude\ Code/instincts/*.md 2>/dev/null | head -20
```

Read any instinct files with similar titles/domains. If an existing instinct covers the same pattern, update it instead of creating a new file.

### Step 4: Write the Instinct File

Filename: `<domain>-<slug>.md` (e.g., `context-management-fork-on-exploration.md`)

```markdown
---
title: <short title>
domain: <domain>
confidence: <0.3–0.9>
trigger: <one-line: when to apply this>
date: <YYYY-MM-DD>
source: <project or "general">
---

## Pattern

<2–4 sentences describing the pattern. What to do, not why.>

## Why It Works

<1–3 sentences: the mechanism behind it.>

## Example

<concrete example — command, code snippet, or scenario>

## When NOT to Apply

<edge cases or conditions where this instinct breaks down>
```

### Step 5: Update the Instinct Index

Check if `instincts/_index.md` exists. If not, create it with a header.
Append one line to `instincts/_index.md`:
```
- [<title>](<filename>) — <trigger>
```

### Step 6: Confirm

Report:
```
Instinct saved: instincts/<filename>
Domain: <domain> | Confidence: <score> | Trigger: <trigger>
```

Files: 1

Size: 2.9 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/ingpoc/skills/tree/main/learn

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