literature-review
# Literature Review
What this skill does
# Literature Review Comprehensive, systematic literature reviews following rigorous academic methodology across biomedical and scientific domains. ## Triggers - User asks for a literature review on a topic - User needs evidence synthesis across multiple studies - User wants to understand the current state of research - User is preparing background for a newsletter or editorial - User needs to identify research gaps ## Workflow Phases ### 1. Planning & Scoping **Define Research Question** using PICO framework: - **P**opulation: Who is being studied? - **I**ntervention: What treatment/exposure? - **C**omparison: Against what? - **O**utcome: What results matter? **Establish Scope**: - Date range (typically 5-10 years for currency) - Study types to include (RCTs, observational, reviews) - Inclusion/exclusion criteria - Languages accepted ### 2. Systematic Search **Required Databases** (minimum 3): | Database | Best For | |----------|----------| | PubMed | Biomedical, clinical | | Cochrane Library | Systematic reviews | | EMBASE | Pharmacology, European | | Google Scholar | Gray literature, coverage | | bioRxiv/medRxiv | Preprints, cutting edge | **Search Strategy Elements**: - MeSH/controlled vocabulary terms - Free-text synonyms - Boolean operators - Field restrictions as needed ### 3. Screening & Selection 1. **Deduplication** - Remove duplicate records 2. **Title screening** - Exclude obviously irrelevant 3. **Abstract review** - Apply inclusion criteria 4. **Full-text evaluation** - Final eligibility check 5. **Document exclusion reasons** at each stage ### 4. Data Extraction Extract from each included study: - Citation information - Study design and setting - Sample size and characteristics - Key findings and effect sizes - Funding sources - Limitations noted by authors ### 5. Quality Assessment | Study Type | Assessment Tool | |------------|-----------------| | RCTs | Cochrane Risk of Bias (RoB 2) | | Observational | Newcastle-Ottawa Scale | | Systematic reviews | AMSTAR 2 | | Diagnostic | QUADAS-2 | ### 6. Synthesis **Critical**: Organize thematically, NOT study-by-study. Bad: "Smith 2020 found X. Jones 2021 found Y. Brown 2022 found Z." Good: "The relationship between SGLT2 inhibitors and heart failure outcomes has been consistently demonstrated across multiple trials (Smith 2020, Jones 2021, Brown 2022), with effect sizes ranging from..." **Identify**: - Areas of consensus - Contradictory findings and potential explanations - Research gaps - Methodological trends ### 7. Citation Verification Before finalizing: - Validate all DOIs against CrossRef - Verify author names and dates - Confirm journal names - Use citation-management skill for formatting ## Output Formats ### For Newsletter Background - Concise synthesis (500-1000 words) - Key statistics highlighted - Top 5-10 most relevant citations - Clear clinical implications ### For Editorial Foundation - Comprehensive synthesis (1500-2500 words) - Organized by theme/controversy - Evidence quality assessment - Explicit gaps identification ### For Academic Manuscript - Full systematic review format - PRISMA flow diagram - Risk of bias tables - Forest plots if meta-analysis ## Best Practices 1. **Document everything** - Search strategies, screening decisions, extraction forms 2. **Search multiple databases** - Minimum 3 for comprehensive coverage 3. **Include preprints** - For most current findings 4. **Assess study quality** - Don't treat all evidence equally 5. **Synthesize thematically** - Never list studies sequentially 6. **Acknowledge limitations** - Search constraints, publication bias 7. **Verify every citation** - Accuracy is non-negotiable
Related in Code Review
gstack
IncludedFast 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)
startup-due-diligence
IncludedLegal 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.
interview-master
IncludedThis 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.
fix-issue
IncludedFixes 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.
sf-apex
IncludedGenerates 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.
swift-development
IncludedComprehensive 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.