self-correcting-loop — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited self-correcting-loop (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill runs an iterative fix → verify → fix cycle on ABAP code until all quality gates pass. It does not stop after one fix attempt — it loops until the code is syntax-clean, ATC-clean, test-passing, and successfully activated.
| Agent Will Try To... | Why It Seems Reasonable | Why It Fails | Counter |
|---|---|---|---|
| Fix multiple errors at once | "I can see three errors, let me fix them all" | Multi-fix creates merge conflicts in your own reasoning. One change triggers side effects in others. | Iron Law 2. One fix per iteration. |
| Suppress ATC findings instead of fixing | "This is a false positive, I'll add a pragma" | If it were a false positive, explain why. Most "false positives" are real findings the developer doesn't want to fix. | Iron Law 5. Fix the code. |
| Skip re-running tests after a fix | "I only changed a comment, tests don't need to re-run" | You think you only changed a comment. Verify. | Iron Law 1. Full check after every fix. |
| Continue past 10 iterations | "I'm so close, one more try" | 10 failed attempts means the approach is wrong. More iterations won't help. | Iron Law 4. Escalate to user. |
| Delete a failing test | "The test is wrong, not the code" | Maybe. Document why the test is wrong. Write a better test. Don't delete evidence. | Iron Law 5. Fix tests, don't delete them. |
<HARD-GATE> Before entering the loop:
If entering from autopilot, these are inherited from the pipeline context. </HARD-GATE>
INITIALIZE
→ Define check suite: [syntax_check, atc_check, unit_tests, activation]
→ Initialize fix history: []
→ Set iteration = 0, max_iterations = 10
LOOP
→ iteration += 1
→ IF iteration > max_iterations: ESCALATE to user with fix history
→ RUN check suite
→ IF all checks pass: EXIT loop → SUCCESS
→ IDENTIFY first failing check
→ ANALYZE root cause of failure
→ APPLY single targeted fix
→ LOG fix to history: { iteration, error, fix_applied, files_changed }
→ GOTO LOOP
EXIT
→ Produce loop summary (iterations, fixes applied, final status)Syntax Check:
ATC Check:
Unit Tests:
Activation:
SELF-CORRECTING LOOP — FIX HISTORY
====================================
Object: [Object name]
Started: [Timestamp]
Check Suite: [syntax, atc, unit_tests, activation]
Iteration 1:
Error: [Error description]
Root Cause: [Analysis]
Fix: [What was changed]
Files: [Modified files]
Result: [Pass/Fail — which check]
Iteration 2:
...
FINAL STATUS: ✅ ALL CHECKS PASS (iteration [N]) / ❌ ESCALATED (iteration 10)
Total fixes applied: [N]This skill is complete ONLY when ALL of the following are true:
Evidence required: Fix history log, final check suite results (all green).
After completing this skill, return to the invoking skill (typically autopilot or code-generation) and continue the pipeline.
autopilot — Primary invoker of this skillcode-generation — May invoke when generated code has issuescode-review — May invoke when review findings need fixestroubleshooting — Invoke if the error is a runtime issue, not a compile-time issue~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.