reasoning

Included with Lifetime

$97 forever

This skill should be used when the user asks to "reason through", "think step by step", "analyze systematically", "debug with hypotheses", "root cause analysis", "chain of thought", "tree of thought", "documentation lookup", or needs structured reasoning frameworks with mandatory documentation retrieval before analysis.

Code Review

What this skill does


# Reasoning Skill

Structured reasoning frameworks with mandatory documentation lookup for systematic problem solving.

## Overview

This skill wraps two complementary capabilities:

1. **Complex Reasoning** (`complex-reasoning.md`) — Multiple reasoning frameworks (Chain-of-Thought, Tree-of-Thought, Hypothesis-Driven Debugging, Root Cause Analysis) that always query documentation before reasoning and store insights in memory.

2. **Documentation Lookup** (`documentation-lookup.md`) — Systematic documentation retrieval using Context7 MCP to ground all decisions in accurate, version-specific library documentation.

## When to Use

- Debugging complex issues where root cause is unclear → use Hypothesis-Driven Debugging
- Making architectural decisions with multiple valid approaches → use Tree-of-Thought
- Linear problem-solving with sequential steps → use Chain-of-Thought
- Systemic incidents or repeated failures → use Root Cause Analysis
- Any task involving external libraries or APIs → use Documentation Lookup first

## Framework Selection

| Problem Type | Framework | Agent |
|-------------|-----------|-------|
| Linear, sequential | Chain-of-Thought | `hypothesis-debugger` |
| Multiple valid approaches | Tree-of-Thought | `requirements-analyzer` |
| Complex bug, unclear root cause | Hypothesis-Driven Debugging | `hypothesis-debugger` |
| Incident, systemic issue | Root Cause Analysis | `root-cause-analyzer` |
| Any technology decision | Documentation Lookup | `requirements-analyzer` |

## Core Protocol

**MANDATORY before any reasoning about technology:**
1. Identify technologies involved in the task
2. Resolve library IDs via Context7 MCP
3. Query relevant documentation
4. Ground all reasoning steps in retrieved documentation

See `complex-reasoning.md` for full reasoning framework details.
See `documentation-lookup.md` for documentation retrieval protocol.

## Integration

Works with: `hypothesis-debugger` (debugging workflows), `root-cause-analyzer` (incident analysis), `requirements-analyzer` (architecture decisions), `task-enricher` (technical planning).

Files: 3

Size: 12.7 KB

Complexity: 25/100

Category: Code Review

Source: https://github.com/lobbi-docs/claude/tree/main/plugins/jira-orchestrator/skills/reasoning

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