skills.rest
PythonShe
PythonSheCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tuner

Diagnose software bugs and verify fixes using rival Codex and Opus investigations.

Updated Jun 2, 2026
Search Tags:#code reliability#software verification#bug debugging#cross-model investigation#test-first repair
One-click install
npx skills add https://github.com/PythonShe/Repertoire --skill tuner-pythonshe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tuner
Source: https://github.com/PythonShe/Repertoire/tree/main/skills/tuner
Command: npx skills add https://github.com/PythonShe/Repertoire --skill tuner-pythonshe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codex, opus, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive approach to debugging, helping users identify the root cause of bugs and verify fixes, resulting in more reliable and maintainable code.

Core Features & Use Cases

  • Cross-model debugging: Utilizes both Codex and Opus agents to ensure thorough debugging.
  • Rival investigations: Two independent investigators ensure a robust diagnosis before any fix is made.
  • Test-first repair: Ensures the fix is effective by requiring a failing test before the fix is applied.
  • Verification: A mechanical verifier confirms the fix works as expected.
  • Use Case: When a bug is reported, the 'tuner' skill can be used to diagnose and fix the issue, ensuring the root cause is addressed and the fix does not introduce new bugs.

Quick Start

Use the 'tuner' skill to debug and fix a reproducible bug in your codebase.

Frequently Asked Questions about tuner

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

FAQPage Schema
How can I find the root cause of a software bug and verify the fix?▼

To find the root cause of a software bug, you can use cross-model investigations where Codex and Opus agents conduct rival investigations. This is followed by test-first repair and mechanical verification to ensure the fix works.

What is a test-first repair approach for software debugging?▼

Test-first repair is a debugging approach that requires writing a failing test to reproduce the bug before applying any fix. This ensures the repair directly addresses the root cause and can be mechanically verified.

Do I need Codex and Opus to use the tuner skill for debugging?▼

Yes, you need access to both Codex and Opus to use the tuner skill. These agents are required to perform the independent rival investigations and subsequent verification tasks for diagnosing software bugs.

How does cross-model investigation improve code reliability?▼

Cross-model investigation improves code reliability by using two independent investigators, Codex and Opus, to robustly diagnose the root cause of a bug. This thorough debugging approach ensures fixes do not introduce new issues.

What is the best way to debug reproducible codebase issues using multiple agents?▼

The best way to debug reproducible codebase issues is using a rival investigation method where Codex and Opus agents independently diagnose the problem. This ensures a robust diagnosis before applying a test-first repair.

When should I not use cross-model debugging for my code?▼

You should not use cross-model debugging when you lack access to both Codex and Opus agents, or when dealing with non-reproducible bugs, as the tuner skill requires both dependencies and a reproducible bug to perform test-first repair.

Related Skills

Explore More Software Engineering Skills→
recallnetrecallnet
1

codex-oracle

Run Codex CLI as an independent agent to review codebase diffs.

Official
Advanced
DmitriyPolukhinDmitriyPolukhin
9

test-driven-development

Enforce test-first development with failing tests before production code.

Community
Advanced
haojing8312haojing8312
154

systematic-debugging

Diagnose and isolate root causes of software bugs and test failures.

Community
Advanced
hydershahhydershah

bug-debugging

Reproduce bugs, isolate root causes, and verify fixes with structured debugging.

Community
Advanced