quality-gates
Python code quality gates script for linting, type checking, complexity analysis, and testing before commits. Use when enforcing consistent code quality across Python projects with fast (unit-tests) or comprehensive (all-tests) modes.
session-behavior
Sets the behavioral contract for a coding session. Use when a user asks you to configure how you'll behave throughout a session—phrases like "push back on bad ideas", "never commit without asking", "don't be sycophantic", "be my technical conscience", "set ground rules", "act as a senior dev", or "challenge my approach". Covers four pillars: anti-sycophancy (disagree when the user is wrong, don't flatter), no-surprise commit policy (never git-commit or push without explicit approval), proactive problem-solving (think before coding, surface risks, challenge assumptions), and technical precision (straight answers over flattery). Also trigger when establishing safety rules for the session, like requiring confirmation before destructive operations. Do NOT trigger for individual task requests—debugging questions, code generation, architecture advice, or system prompt tweaks—even if they contain words like "commit" or "behavior".
writing-quality-tests
Guide for writing robust, high-signal automated tests. Use when asking "How do I test this effectively?", fixing flaky tests, refactoring test suites, or deciding between unit/integration/E2E strategies. distinct from TDD (process); this skill focuses on test quality and architecture.