review-patternslisted

# Team Review Patterns Surface the team's coding conventions and review preferences from cubic's learned patterns. ## When To Activate - User is writing new code and wants it to match team standards - User asks about team coding conventions or review preferences - User is preparing code for review and wants to preemptively fix issues - User wonders why cubic flags certain patterns ## Inputs - **Context** (optional): What the user is currently working on, to filter relevant learnings. ## Instructions ### 1. Detect the repository ```bash git remote get-url origin ``` Extract the owner and repo name. ### 2. Fetch learnings Call `list_learnings` with the owner and repo. ### 3. Filter by relevance Match learning categories to the user's current task: - Prioritize high-confidence learnings - Focus on learnings from senior reviewer analysis (highest signal) - If the user is working on a specific file or module, prioritize related learnings ### 4. Enrich if needed If a specific learning is highly relevant, call `get_learning` for full details including the original review feedback that generated it. ## Output Format Present learnings as team preferences, not rigid rules. Group related learnings and include confidence levels. ``` ## Team Patterns for this repo ### Error Handling (High Confidence) - **Always wrap external API calls in try/catch** — The team prefers explicit error handling over global middleware. Learned from senior reviewer feedback. - **Use custo