requesting-code-review
[ Featured ]requesting-code-review is a skill that enables developers to request code reviews, ensuring work meets requirements through subagent-driven evaluation
Browse and install thousands of AI Agent skills in the Killer-Skills directory. Supports Claude Code, Windsurf, Cursor, and more.
requesting-code-review is a skill that enables developers to request code reviews, ensuring work meets requirements through subagent-driven evaluation
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when a user asks a business question that requires querying data (e.g., What were total sales last quarter?). NOT for validating, testing, or building dbt models during development.
Clarify requirements before implementing. Do not use automatically, only when invoked explicitly.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Ingest data from S3 into bauplan using the Write-Audit-Publish pattern for safe data loading. Use when loading new data from S3, performing safe data ingestion, or when the user mentions WAP, data ing
Automatically rewrites, expands, and enhances user requests using proper linguistics and structured input for optimal vibe coding and SaaS development results
Crowdsourced forecasting questions and predictions from the RAND Forecasting
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management quest
Testing guide using Vitest. Use when writing tests (.test.ts, .test.tsx), fixing failing tests, improving test coverage, or debugging test issues. Triggers on test creation, test debugging, mock setup
Clarify scope through dialogue, surface key decisions and open questions. Use before planning.