← all publishers

MegaBadCoder

@megabadcoder source repo

Report this profile Claim this profile

• 23 skills
• 0 followers
• 5 hours ago last updated

1. ▌
   Quickfix · megabadcoder

   Small bugs and single-file edits without ceremony — reproduce → hypothesis → minimal fix → test. Use when the user invokes /quickfix, or when a task turns out trivial (one-file CSS tweak, typo, missing import, single-line logic fix). Never commits — the user commits.
   0 installs
2. ▌
   Eli Intern · megabadcoder

   Explain like to a competent intern — technically complete and precise, assuming general programming skill but zero knowledge of *this* codebase, its history, and its conventions. Use when the user says "elii", "eli-intern", "объясни как стажёру", "как новому разработчику", "введи в контекст", or when onboarding someone onto a subsystem. The top rung above eli14 — no simplification of the mechanism, only of the assumed context.
   0 installs
3. ▌
   E · megabadcoder

   Explain a file, error, design, diff, or concept like a helpful engineering colleague: grounded in evidence, concise, and with useful follow-up threads. Use when the user asks for a clear explanation of the current work or codebase.
   0 installs
4. ▌
   Try · megabadcoder

   Manually test the latest change with one realistic positive case and one adversarial negative case, capturing evidence before any further fix. Use when the user asks for a quick confidence check or wants to test a recent implementation.
   0 installs
5. ▌
   Make · megabadcoder

   Orchestrate the full Ultrapack workflow in Codex: create or resume a task file, design, plan, execute, verify, review, and validate the observable goal. Use when the user asks to build, fix, or deliver a non-trivial change with the complete workflow.
   0 installs
6. ▌
   Uplan · megabadcoder

   Use after design to turn a validated spec into a lean implementation plan. Outputs the `## Plan` section of the task file — files, line numbers, class/method names, invariants, test strategy, order. Ends with a scope-creep / simpler-way check.
   0 installs
7. ▌
   Udebug · megabadcoder

   Use on any bug, test failure, or unexpected behavior before proposing a fix. Enforces four-phase root-cause investigation — reproduce, pattern-match, hypothesize, fix — with a hard rule against symptom patches.
   0 installs
8. ▌
   Reflect · megabadcoder

   Extract durable, non-obvious lessons from the current dialogue and route them to project guidance, memory, documentation, or the active task conclusion. Use when the user asks to reflect on a session or preserve learnings.
   0 installs
9. ▌
   Summary · megabadcoder

   Produce a compact, zero-context handoff for the current Codex work and, after user confirmation, save it to the active task conclusion or a new task summary file. Use when the user asks to preserve progress for a later session.
   0 installs
10. ▌
    Udesign · megabadcoder

    Use before any creative work — features, components, behavior changes. Turns an idea into a validated spec with explicit tradeoffs and unknowns, and splits scope into multiple tasks if it's too large. Output is the `## Context` and `## Design` sections of the task file.
    0 installs
11. ▌
    Eli5 · megabadcoder

    Explain something as if to a five-year-old — one physical-world analogy carried all the way through, no jargon, short sentences. Use when the user says "eli5", "explain like I'm five", "объясни как пятилетнему", "как для ребёнка", "совсем просто", or when their questions show they're lost in terminology rather than in the idea. Also use proactively mid-explanation when the user says "не понимаю" / "I don't get it" twice about the same thing — switch levels instead of repeating yourself louder.
    0 installs
12. ▌
    Eli14 · megabadcoder

    Explain at the level of a bright fourteen-year-old — real terms allowed but each one unpacked on first use, analogies to support the mechanism rather than replace it. Use when the user says "eli14", "объясни как школьнику", "попроще, но по-настоящему", or when ELI5 landed and they want the actual mechanism next. The middle rung between eli5 (no terms at all) and eli-intern (full technical, just no project context assumed).
    0 installs
13. ▌
    Learn · megabadcoder

    Socratic teaching mode that verifies the user deeply understands code — not just that it works. Use whenever the user wants to understand, learn, review, or be quizzed on code: a coding session just completed, an existing file/module/feature, a PR or diff, recent commits, an unfamiliar part of a repo, or the structure of code — how functions, classes, and modules relate (call graphs, ownership, inheritance, data flow). Trigger on phrases like "explain this code", "help me understand", "teach me what we did", "how do these functions/classes connect", "разбери код", "объясни", "как связаны функции/классы", "проверь моё понимание", "quiz me", or when the user asks to review what was built. Also use proactively after substantial implementation work if the user signals they want to learn, not just ship.
    0 installs
14. ▌
    Ureview · megabadcoder

    Use after verify passes for the future maintainer's audit — sit in the chair of the person who'll touch this code in 3-6 months and ask "what will bite us later?" at the decision level. Surfaces wrong abstractions, load-bearing-but-unobvious shapes, next-change traps, drift from surrounding code; raises a Scope flag if the whole change looks like the wrong call. Delegates an independent, critical review and fills the task file's `## Conclusion`.
    0 installs
15. ▌
    Uverify · megabadcoder

    Use after execute to attack the change and demonstrate how it's broken. Default stance — the change is broken; prove and demonstrate it. Builds an attack checklist (happy-path / negative / invariant / interface hypotheses), runs each freshly, smokes the end-to-end, writes a short summary to the task file's Verify section, loops back to execute on any demonstrated break.
    0 installs
16. ▌
    Handsoff · megabadcoder

    Contract for hands-off mode — the ultrapack workflow variant that minimizes user prompts after Design, takes the safest reversible path, and logs every auto-choice for one end-of-task review. Referenced by the workflow entry point and child skills (udesign, uplan, uexecute, uverify, ureview). Read when the task file's **Mode:** header is `hands-off`.
    0 installs
17. ▌
    Uexecute · megabadcoder

    Use to implement an approved plan. When the plan declares `### Interface graph`, derives waves by topo-sort over `[blocks]` IF edges only — non-blocking IF edges (the default) put producer and consumer in the same wave, since the IF declaration is sufficient context. Edits inline when only one implementer would fire (single phase or serial fallback). Runs plan-diff check and consistency sweep after each commit. Forbids silent fallbacks and mutation of external spec/design docs. Dispatches the planner skill when deviations invalidate the plan.
    0 installs
18. ▌
    Step Back · megabadcoder

    Break a failed implementation loop by tracing attempts, identifying the real blocker, and proposing a materially different direction before further changes. Use when repeated fixes or investigations are not converging.
    0 installs
19. ▌
    Udocument · megabadcoder

    Use when writing or editing documentation — project docs, CLAUDE.md, READMEs, SKILL.md, docstrings, inline comments. Auto-triggers on `.md` files and docstring edits. Enforces lead-with-why, kill stale content, lists over tables, no aspirational sentences.
    0 installs
20. ▌
    Attack Loop · megabadcoder bundle

    Run a bounded implement-attack-repair loop for a user-specified task. Use when work needs repeated independent criticism: perform the task, dispatch a fresh attacker, verify significant findings, repair them, and stop on a clean attack or the user's round limit.
    0 installs
21. ▌
    Job Guardian · megabadcoder

    Use to babysit a long-running process (training run, batch job, migration, deploy) on a remote pod or locally while the user is away. Defines a launch contract, gates on immediate crash, polls for stability, triages anomalies as recoverable (fix + resume) or not (tear down + notify). Auto-triggers when the user asks you to launch a job and watch it / keep it alive / shut it down if it dies.
    0 installs
22. ▌
    Git Worktrees · megabadcoder

    Use when a task needs isolation from the current workspace. Picks a worktree directory via a fixed priority order, verifies it's gitignored, creates the worktree, auto-detects project setup, runs baseline tests.
    0 installs
23. ▌
    Test Driven Development · megabadcoder

    Use when implementing deterministic, reusable code where regressions would warrant a CI red light. Enforces RED-GREEN-REFACTOR. Applicability rule and skip conditions inside.
    0 installs