Skill

Ask WeZZard

Report attune plugin failures as scrubbed issues in one step.

Use in Claude Code
/attune:ask-wezzard

Ask WeZZard turns a broken attune skill or guideline into a structured GitHub issue, automatically scrubbing user-side detail and quoting the failing agent output verbatim. It distinguishes communication failures that feed the improvement loop from skill failures that name the broken protocol step. When gh is unavailable, the filled template prints in-session so no report is ever lost.

Key Insights

Two failure channels

Communication failures carry the extraction template the collect-feedback-and-improve loop consumes; skill failures carry the general template plus the skill and step that failed. Each lands under its own label.

Verbatim, scrubbed reports

Your own failing output is quoted word-for-word, while the user's reaction is paraphrased and no project code, secrets, or paths outside the plugin are included. Reports stay useful without leaking context.

Authoritative model detection

Reads the exact model ID from your system prompt on claude-code, or from attune's session-model store on codex and pi, with a rollout-file fallback. It writes unknown only when every source yields nothing.

Never-silent failure

If gh is missing, unauthenticated, or offline, the filled template prints in the conversation instead of being discarded. The report always reaches a human reviewable form.

How It Works

1

Classify the failure

Decide communication vs. skill failure.

Determine whether a reply broke the communication guidelines or another attune skill or guideline behaved wrongly, since each type takes a different template and label.

2

Collect context

Gather quotes, reaction, repair, and session info.

Quote your failing output verbatim, paraphrase the reader's reaction in one line, propose a repair, and record language, platform, and model from the authoritative source for your platform.

3

File the issue

Create one labeled issue per failure.

Run gh issue create against WeZZard/attune with the matching template and label, one issue per distinct failure so nothing is bundled or dropped.

4

Report back or fall back

Share the URL, or print the template.

Give the user the issue URL; if gh fails for any reason, print the filled template in the conversation so the report is never lost silently.