Skill UI

Performs a structured, multi-phase audit on local branch changes (diffs) to identify security vulnerabilities, bugs, and code quality issues. It systematically checks for common risks like Injection (SQL, XSS), Broken Authentication, IDOR, CSRF, and business logic flaws, providing detailed severity, evidence, and suggested fixes. Ideal for pre-merge code reviews and security audits.

This skill provides comprehensive guidance for the entire lifecycle of Conductor tracks—the logical work units used to organize features, bugs, and refactors. It assists users in creating, reviewing, updating specifications (spec.md), developing plans (plan.md), and managing the status and metadata of tasks from initial conception through final completion, ensuring structured and traceable development processes.

Test-Driven Development (TDD) is a software development methodology where tests are written before the actual code. It follows the Red-Green-Refactor cycle to ensure code quality and reliability. Use this skill when implementing new logic, fixing bugs, or modifying existing functionality to prove correctness. It helps prevent regressions and creates a robust codebase suitable for AI agents.

An adversarial Quality Assurance (QA) pass designed to deep-dive into any codebase for logic errors, security flaws, and functional bugs. Instead of confirming that code 'looks right,' this skill actively attempts to break the code by simulating hostile inputs, tracing critical data paths, and checking for subtle, real-world correctness issues. Essential for high-stakes, critical code reviews.

This skill provides an autonomous, repository-wide pipeline for auditing and fixing complex logical inconsistencies. It systematically executes stages including health checks, deep review, locating divergences, generating fixes, and performing diff-verification until the codebase is deemed clean. Ideal for maintaining high code quality and resolving deep, systemic bugs across entire projects.

This skill is designed to identify subtle and complex logic bugs within a single code file or function. It employs a semi-formal execution tracing methodology, systematically breaking down the suspected bug into five stages: Premises (expected state), Trace (execution path), Divergence (actual deviation), Trigger (reproduction case), and Remedy (fix). It is ideal for scenarios where users suspect code is wrong but cannot specify a concrete failure point.

This diagnostic skill audits the entire local setup of Claude Code against several known, complex cache and cost bugs (CC#40524, B4, B5). It checks critical components including version compatibility, sentinel placeholders, session resuming logic, and attribution headers. Use this tool to ensure your development environment is optimized, stable, and minimizes unexpected operational costs and functional regressions.

Analyzes code changes to identify concrete defects such as bugs, logic errors, and edge-case failures. A practical assistant for development teams verifying pull requests and code revisions.

An adversarial Quality Assurance (QA) pass designed to deep-dive into any codebase for logic errors, security flaws, and functional bugs. Instead of confirming that code 'looks right,' this skill actively attempts to break the code by simulating hostile inputs, tracing critical data paths, and checking for subtle, real-world correctness issues. Essential for high-stakes, critical code reviews.

Logic Lens is an AI-powered code review skill that uses formal logic frameworks to detect bugs, anti-patterns, and security risks beyond linters. It covers 9 risk categories including null handling, type safety, concurrency, and security injection, providing severity-ranked findings with fix suggestions.

Find logic bugs in code files or functions through semi-formal execution tracing methodology. Analyzes Premises, Trace, Divergence, Trigger, and Remedy to identify and fix logical errors in programming code. Suitable for code review when users suspect issues without naming concrete failures.

This skill provides comprehensive guidance for the entire lifecycle of Conductor tracks—the logical work units used to organize features, bugs, and refactors. It assists users in creating, reviewing, updating specifications (spec.md), developing plans (plan.md), and managing the status and metadata of tasks from initial conception through final completion, ensuring structured and traceable development processes.