Debug off

Skill ievo-ai/skills/plugins/ievo/skills/debug-off

iEvo — self-evolving plugin for Claude Code. Capture lessons, patch local agents and skills, replay logs on upstream updates.

Install

npx -y skills add ievo-ai/skills --skill debug-off

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use this skill when debugging is complete and the user wants to stop accumulating large trace logs — trigger words "turn off debug", "stop verbose", "disable trace", "debug off". Disables verbose / trace-level logging for the iEvo pipeline. Reverts to normal logging (concise `.ievo/log/init-*.md` only).

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

4.3 KB, as published. Nobody here has run it

Debug Off — disable verbose session logging

Reverts iEvo skills to their default concise logging mode. Removes .ievo/debug.flag. Existing debug session logs in .ievo/log/debug/<session-id>/ are NOT deleted — they're preserved as audit artifacts.

Claude Code v2.1.181+ alternative. If you only turned on Claude Code's own verbose output via /config verbose=true (see /ievo:debug-on's note) rather than this skill, turn it back off the same way: /config verbose=false. This skill's flag removal only clears .ievo/debug.flag — it never touches Claude Code's verbose setting either way.

When to use

User says "turn off debug", "stop verbose", "disable trace", "debug off"
After filing a bug report and no longer needs accumulating logs
Disk pressure from large debug logs

Steps

1. Check if debug is currently on

If <project>/.ievo/debug.flag does not exist → already off. Tell user:

iEvo debug mode is already OFF (no .ievo/debug.flag found).
Past debug logs (if any) remain in .ievo/log/debug/.

Exit.

2. Read flag content for the closing summary

Read .ievo/debug.flag and capture:

enabled_at (when debug was turned on)
enabled_by
reason

3. Remove the flag

POSIX hosts (macOS / Linux / WSL) — use Bash with rm -f for idempotence:

rm -f <project>/.ievo/debug.flag

Windows hosts (PowerShell, no POSIX shell):

Remove-Item -ErrorAction SilentlyContinue '<project>\.ievo\debug.flag'

Cross-platform fallback via the Bash tool if Node is available:

node -e "try { require('fs').unlinkSync('<project>/.ievo/debug.flag') } catch (e) { if (e.code !== 'ENOENT') throw e }"

(No Write-tool equivalent — there's no "delete" operation in Write. The narrow-scope rm/Remove-Item/unlink targets a specific named file with no glob, no recursion, and is idempotent — handles the race between Step 1's existence check and this step.)

4. Find the active session directory

<project>/.ievo/log/debug/ may contain multiple session subdirs. Find the most recent (alphabetical sort = chronological since ISO basic format). That's the session being closed.

5. Drop a session end marker

Write <project>/.ievo/log/debug/<latest-session-id>/99-session-end.md:

# Debug session ended — <ISO-8601 UTC>

- Started: <enabled_at from flag>
- Duration: <wall-clock>
- Closed by: <user invocation>
- Reason for closing: <if provided>

Logs preserved at: .ievo/log/debug/<session-id>/

6. Confirm to user

Print to user:

🔬 iEvo debug mode DISABLED

Session preserved at: .ievo/log/debug/<session-id>/
Session contents: <file count>, <total size>

If filing a bug: archive that directory (e.g. `tar czf debug-<session-id>.tgz .ievo/log/debug/<session-id>/` on POSIX, `Compress-Archive` on Windows) and attach.

Re-enable: /ievo:debug-on

For the file count + size, use whatever the host shell supports — ls + du on POSIX, Get-ChildItem | Measure-Object on Windows PowerShell, or Node fs.readdirSync().length + recursive walk if neither is available. The user-facing summary just needs a count and a size; the specific tooling is host-dependent.

Rules

Non-destructive: do NOT delete .ievo/log/debug/ contents. The flag goes away, the logs stay.
Idempotent: if already off, just say so. No error.
Preserve audit trail: even if user later does debug-on again, prior sessions are kept under their own session-ids.