Skill UI

Prepares codebases for Trail of Bits security reviews by setting goals, running static analysis, expanding test coverage, pruning dead code, documenting build scope/access, and generating flowcharts, user stories, glossaries, and other reviewer-ready artifacts.

Prepares codebases for Trail of Bits security reviews by setting goals, running static analysis, expanding test coverage, pruning dead code, documenting build scope/access, and generating flowcharts, user stories, glossaries, and other reviewer-ready artifacts.

This expert tool automates compliance checks for EU GDPR and German DSGVO. It scans codebases for privacy risks (PII, special data), generates formal Data Protection Impact Assessments (DPIA), and manages the entire lifecycle of Data Subject Access Requests (DSARs), ensuring adherence to strict legal deadlines. Ideal for privacy audits and compliance planning.

This skill simulates a senior engineer's final, deep audit of an entire codebase before committing or pushing to a remote repository. It systematically checks for junk files, dead code, security vulnerabilities (secrets, injection flaws), and performance bottlenecks (N+1 queries). Use this pre-flight check before any major release or public deployment to ensure maximum code quality and production readiness.

A specialized tool for auditing source code (C/C++/Rust) to ensure sensitive data (keys, passwords, PII) is properly zeroized. It analyzes memory handling at the assembly and IR level to detect if compiler optimizations, such as dead-store elimination, have accidentally removed or weakened the secure cleanup process. Essential for maintaining security in critical codebases.

Runs the Centinela QA agent to scan for dead code, tech debt, outdated or vulnerable dependencies, code smells, and TODO/FIXME audit results, generating a documented report for release or refactor readiness.

An advanced debugging skill designed for AI agents. It utilizes gdb-cli to provide intelligent assistance for C/C++ programs, enabling the analysis of core dumps, debugging live processes, and investigating complex issues like crashes, deadlocks, and memory corruption. It correlates runtime state inspection with source code context for deeper insights.

Provides a structured process for deprecating legacy systems, APIs, and features, and migrating consumers to replacements. Useful for sunsetting code, removing dead code, performing expand/contract database migrations without downtime, and deciding whether to maintain or retire existing software. Covers migration patterns, timelines, and best practices.

A comprehensive guide for designing, implementing, and reviewing scalable microservices using gRPC in Go. It covers critical best practices including structured protobuf organization, implementing interceptors for cross-cutting concerns, managing connection deadlines, handling standardized gRPC status codes, and ensuring graceful shutdown for robust distributed systems.

This guide provides comprehensive best practices for writing robust and high-performance asynchronous code in C#. It covers naming conventions, optimal return types (Task, ValueTask), advanced patterns like the async command pattern, proper exception handling, and crucial performance considerations (e.g., using Task.WhenAll() and avoiding deadlocks with ConfigureAwait(false)). Ideal for developers looking to master modern C# concurrency.

This skill performs comprehensive, systematic cleanup across 11 critical dimensions of code quality, including dead code removal, security vulnerability checks, weak type elimination, and performance optimization. It analyzes code, assigns confidence scores, and verifies all suggested changes using build and test gates. Ideal for projects suffering from accumulated technical debt, or before major release cycles to ensure robust, maintainable code.

This guide provides a systematic, safe workflow for refactoring rapidly developed or AI-generated fullstack applications. It focuses on identifying and removing dead code, fixing broken imports, and consolidating repetitive logic while strictly maintaining existing API contracts, routes, and core functionality. Use this before launch to ensure a stable, maintainable production baseline, following a 'surgery, not demolition' philosophy.