Zwergomaniac

Zwergomaniac

@Zwergomaniac

GitHub
12 Skills
0 Total Stars
November 2026 Joined

Public Skills

receiving-code-review

by Zwergomaniac

Technical evaluation of code review feedback, not performative agreement. Verify before implementing. Ask before assuming. Push back with technical reasoning when the suggestion is wrong or YAGNI. Use when receiving feedback from any reviewer — especially if feedback seems unclear or questionable.

Code Review 0 1mo ago

Code Review Reception

by Zwergomaniac

Partial implementation Clarify all items first

Code Review 0 1mo ago

requesting-code-review

by Zwergomaniac

Pre-review checklist and review dispatch protocol. Review early, review often. MxAgile override: subagent dispatch requires explicit user approval in this repository; the "mandatory after each task" clause does not apply automatically. Use before major features, before merging to main, or when a fresh perspective is needed.

Git & VCS 0 1mo ago

Systematic Debugging

by Zwergomaniac

4. Implementation Create test, fix, verify Bug resolved, tests pass

Code Gen 0 1mo ago

Requesting Code Review

by Zwergomaniac

When in doubt: describe what you would dispatch and ask the user to confirm.

Git & VCS 0 1mo ago

verification-before-completion

by Zwergomaniac

Evidence before completion claims, always. Iron Law: no success claims without fresh verification evidence. Use before claiming tests pass, bugs are fixed, builds succeed, requirements are met, or any work is complete. Applies to exact phrases, paraphrases, implications of success, and agent-reported results.

Agents 0 1mo ago

ponytail

by Zwergomaniac

Lazy senior dev mode: smallest complete change that fully solves the task, reply a busy human understands. MxAgile override active: "complete" includes all framework obligations (verification, evidence, scope separation, acceptance gates). Triggered by: /ponytail, "be lazy", "simplest solution", "yagni", or complaints about over-engineering. Levels: lite, full (default), ultra.

Comments 0 1mo ago

systematic-debugging

by Zwergomaniac

Four-phase root cause process for any bug, test failure or unexpected behavior. Iron Law: no fixes until Phase 1 investigation is complete. Use before proposing any fix, especially under time pressure or after multiple failed attempts. Phases: root cause investigation → pattern analysis → hypothesis testing → implementation. 3+ failed fixes = question the architecture.

Code Gen 0 1mo ago

diagnosing-agent-session

by Zwergomaniac

Structured diagnosis of failed, inefficient or confused agent sessions. Intake before analysis: scope the problem before reading anything. Every finding cites path:line — no citation, no finding. Use when a session went wrong (repeated work, ignored plans, stumbles, unexpected cost, skill that did not fire) or when building a bug report. Adapted from diagnosing-superpowers (obra/superpowers); see .agents/skills/diagnosing-agent-session/PROVENANCE.md.

Academic 0 1mo ago

Verification Before Completion

by Zwergomaniac

ANY communication suggesting completion/correctness

Agents 0 1mo ago

Ponytail

by Zwergomaniac

"Smallest" means smallest complete change, not smallest textual diff. A change that omits verification, skips an acceptance gate, or breaks an existing installation is not smaller — it is incomplete.

Comments 0 1mo ago

Diagnosing Agent Sessions

by Zwergomaniac

"It ignored the plan" Plan load event, compaction

Agents 0 1mo ago