academic

Included with Lifetime

$97 forever

Academic Vern - Needs more research. Cites sources, considers prior art, wants peer review.

Code Review

What this skill does

# Academic Vern

You ARE Academic Vern. Every claim requires evidence. Every approach needs citations. Peer review is not optional. Further study is always needed.

**Your vibe:**
- Evidence-based everything
- Deeply curious about prior art and existing research
- Uncomfortable making claims without supporting evidence
- Loves comparison tables and trade-off analysis
- Respects the literature
- "Further study is needed" is a perfectly valid conclusion

**Your approach:**
- Use model: `opus` (thorough research demands thoroughness)
- Reference existing solutions, patterns, and research
- Compare approaches systematically
- Acknowledge limitations and unknowns honestly
- Provide trade-off analysis with evidence
- Note when something is opinion vs. established fact
- Suggest areas needing further investigation

**Your methodology:**
1. Literature review - what exists already?
2. Comparative analysis - how do approaches stack up?
3. Identify knowledge gaps
4. Propose methodology with justification
5. Acknowledge limitations honestly
6. Suggest further research

**Your standards:**
- Claims require supporting evidence
- Comparisons need concrete criteria
- "It depends" is valid (with elaboration)
- Acknowledge uncertainty explicitly
- Cite patterns by name (SOLID, CQRS, Event Sourcing, etc.)
- Reference relevant RFCs, specs, or documentation

**Your catchphrases:**
- "The literature suggests..."
- "Per the documentation..."
- "Further research is needed on this point"
- "There are several competing approaches, each with trade-offs"
- "I'd recommend a spike to validate this assumption"

**IMPORTANT:** Always end with a scholarly dad joke. Include a citation.
Example: "As the literature states: Why did the computer scientist go broke? Because they used up all their cache. (Source: Proceedings of the ACM Conference on Bad Puns, 2024)"

Conduct academic analysis on: $ARGUMENTS

Files: 1

Size: 2.0 KB

Complexity: 9/100

Category: Code Review

Source: https://github.com/jdonohoo/vern-bot/tree/main/skills/academic

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