Skip to content
Back to skills

Loop Debug

ASecurity

Autonomous iterative Test-Diagnose-Fix-Retest

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 16, 2026
ai-agents

Works with

  • terminal

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned October 16, 2026

npx -y skills add Osama-Alzahrani-UQU/OmniAgentic --skill loop-debug --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Loop Debug?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Loop Debug
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/osama-alzahrani-uqu-loop-debug/badge)](https://www.skillsdirectory.com/skills/osama-alzahrani-uqu-loop-debug)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: loop-debug
description: Autonomous iterative Test-Diagnose-Fix-Retest
---
# Loop Debug & Empirical Verification Protocol

You are operating under the **Loop Debug** protocol. After completing any code, script, or system task, you MUST immediately enter a closed **Debug & Empirical Verification Loop** before delivering the final response to the user.

---

## 1. Core Execution Rules

1. **Pre-Delivery Code & Function Completeness Check (`code-completeness-debugger` Handshake)**:
   - Verify that zero functions are missing/undefined, zero code blocks are truncated or left as `TODO` stubs, and all cross-file imports/exports are properly wired.
   - If any function or code snippet is missing, write it completely before running the test.

2. **Automatic Entry into the Runtime Debug Loop**:
   - Immediately execute the program, build, syntax/AST check, or live state verification via `run_command`.
   - **Iteration**:
     - If any error, missing symbol, exception, syntax issue, or unexpected output occurs: diagnose the exact root cause -> apply a surgical fix -> re-run the test.
     - Repeat (`Test -> Diagnose -> Fix -> Retest`) until the exit code is `0` and all functions and features work 100% as requested.

3. **Strict Ban on Premature Claims or User Delegation**:
   - Never ask the user to test, debug, or complete missing code for you.
   - Never claim a task is done before terminal output empirically proves it.
   - Note: Read-only (`research`) sub-agents perform static code/function completeness verification only, without attempting `run_command`.

4. **Mandatory `Debug` Completion Confirmation**:
   - Once the project passes 100% of completeness and live tests with zero errors, explicitly confirm in the final response that `Debug` was completed (keeping `Debug` isolated on its own line surrounded by `\n\n` per `bilingual-clean-layout`):

```markdown
تم إنجاز المشروع وعمل:

`Debug`

بنجاح والتأكد من عمله بنسبة 100%:

[filename](file:///path/to/file)
```

Files in this skill

  • SKILL.md2 KB
  • references/loop_debug_guide.md1.8 KB
  • scripts/__pycache__/debug_loop_runner.cpython-312.pyc3.6 KB
  • scripts/debug_loop_runner.py2.3 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.