debug

Identify logic flaws, bugs, bottlenecks, vulnerabilities, and test gaps in code.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/discountry/ritmex-skills --skill debug-discountry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/discountry/ritmex-skills/tree/main/skills/debug
Command: npx skills add https://github.com/discountry/ritmex-skills --skill debug-discountry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually hunting for bugs, security vulnerabilities, and performance bottlenecks across large or recently changed codebases is time-consuming and error-prone, especially when the root cause of an issue is not immediately obvious.

Core Features & Use Cases

  • Multi-Dimension Analysis: Systematically checks for logic errors, latent bugs, performance inefficiencies, security flaws, and missing test coverage, with a focus on recently modified code where most defects originate.
  • Root Cause Focus: Goes beyond surface-level symptoms to identify the exact change or code pattern that introduced the issue, paired with targeted fix recommendations.
  • Use Cases: Review recent commits for regressions after a deployment, audit code for security vulnerabilities before a production release, or investigate unexplained performance slowdowns in a feature you just updated.

Quick Start

Use the debug skill to review the changes in my last 3 commits and identify any potential bugs or security issues.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find security vulnerabilities and logic bugs in recent code commits?

To find security vulnerabilities and logic bugs in recent commits, systematically review recently modified files and staged changes. This approach narrows the search surface to the most likely source of defects, providing ranked issues with root cause analysis and fix recommendations.

What is the best way to perform a pre-release security audit on an existing codebase?

A pre-release security audit systematically checks existing codebases for latent security flaws, logic errors, and performance bottlenecks. It applies to all programming languages and frameworks, identifying exact code patterns that introduced vulnerabilities before production release.

How do I identify the root cause of a performance bottleneck after a deployment?

Identify the root cause of a performance bottleneck by reviewing recent commits for regressions. This process goes beyond surface-level symptoms to pinpoint the exact code change that introduced the inefficiency, paired with targeted fix recommendations.

Can I use automated code review to detect missing test coverage in my project?

Automated code review can detect missing test coverage by systematically analyzing existing codebases. It identifies gaps in test coverage alongside logic flaws and security vulnerabilities, focusing on recently modified files where most defects originate.

Does automated bug detection work across different programming languages and frameworks?

Automated bug detection works across all programming languages and frameworks for use cases including regression review, security auditing, and performance troubleshooting. It prioritizes recently modified files and recent commits to narrow the search surface.

Why should I focus code review on recently modified files rather than the entire codebase?

Focusing code review on recently modified files narrows the search surface to the most likely source of defects, as most bugs and security gaps originate in recent changes. This targeted approach is faster and less error-prone than manually hunting across the entire codebase.