MGallo-Code

MGallo-Code

@MGallo-Code

GitHub
28 Skills
0 Total Stars
October 2026 Joined

Public Skills

coding-mastermind-cross-check

by MGallo-Code

Runs a rare, high-stakes decision or diff past other-vendor flagship CLIs (Codex, Gemini) in read-only/sandboxed mode, prompting them to REFUTE it, then synthesizes one PROPOSAL that preserves the disagreement. Adversarial cross-check, NOT a majority vote. Use only for high-stakes or large-diff or strategic decisions; skip on Q&A and small edits.

CLI Tools 0 today

coding-mastermind-update

by MGallo-Code

The single owner of agent-platform drift. Upgrades the installed coding-agent CLIs (Claude Code, Codex, Gemini, and any others) each via its REAL install channel, then re-stamps the kit's MANIFEST baseline and re-verifies the capability facts the kit depends on - proposing the MANIFEST diff, never auto-applying it. Use when the user says "update/upgrade my agents/tools", on a new Claude Code/Codex/Gemini release, on a periodic tooling refresh, or to re-verify the baseline without upgrading (check-only).

CLI Tools 0 today

doubt-driven-development

by MGallo-Code

Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now than to debug later.

CLI Tools 0 today

build-orchestration

by MGallo-Code

Run Michael's Orchestrator/Builder/Challenger build system on a project. Covers setting up worktrees and briefs, the Orchestrator's continuity through a resume card, a fresh Challenger subagent per candidate, a Builder per slice, role guards, per-role models and the pilot metrics. Use when Michael asks to orchestrate a build, start or continue an orchestration, or run the build/critique system.

Git & VCS 0 1d ago

calendar

by MGallo-Code

Create, view, or manage Google Calendar events via the first-party calendar MCP. Activate when the user says calendar, schedule, book, event, meeting, availability, or asks what's on the calendar.

Auth 0 2d ago

coding-mastermind-init

by MGallo-Code

Scaffolds the coding-mastermind kit into a repo - a short layered CLAUDE.md, an INVARIANTS registry stub, a Definition-of-Done, and a PR template - so an agent reuses what exists and every cross-cutting invariant has a named enforcer. Use when onboarding a repo to the kit, when a repo keeps re-breaking the same invariant, or when asked to "harden this repo" or "set up coding-mastermind here."

Code Gen 0 2d ago

coding-mastermind-audit

by MGallo-Code

The low-frequency BACKSTOP that keeps a repo's INVARIANTS registry honest - re-checks every enforcer still fires, finds NEW surfaces a covered invariant's gate does not yet see, refreshes recurrence counts, and surfaces a short ranked "what's overdue." Read-only detection that proposes, never edits. Use periodically or when asked to audit the invariants registry; it does NOT depend on the cross-vendor CLIs.

Code Review 0 2d ago

security-and-hardening

by MGallo-Code

Hardens code against vulnerabilities. Use when handling user input, authentication, data storage, or external integrations. Use when building any feature that accepts untrusted data, manages user sessions, or interacts with third-party services.

Auth 0 2d ago

git-workflow-and-versioning

by MGallo-Code

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump, tagging, or writing a changelog.

Git & VCS 0 2d ago

observability-and-instrumentation

by MGallo-Code

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

API Dev 0 2d ago

shipping-and-launch

by MGallo-Code

Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.

Accessibility 0 2d ago

incremental-implementation

by MGallo-Code

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.

Code Gen 0 2d ago

using-agent-skills

by MGallo-Code

Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

CI/CD 0 2d ago

spec-driven-development

by MGallo-Code

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

Templates 0 2d ago

frontend-ui-engineering

by MGallo-Code

Builds production-quality UIs. Use when building or modifying user-facing interfaces. Use when creating components, implementing layouts, managing state, or when the output needs to look and feel production-quality rather than AI-generated.

Accessibility 0 2d ago

performance-optimization

by MGallo-Code

Optimizes application performance. Use when performance requirements exist, when you suspect performance regressions, or when Core Web Vitals or load times need improvement. Use when profiling reveals bottlenecks that need fixing.

Design 0 2d ago

code-review-and-quality

by MGallo-Code

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

Code Review 0 2d ago

coding-mastermind-help

by MGallo-Code

Explains how to use the coding-mastermind kit in under a screen - what is automatic and global vs per-repo, how to harden a new repo, when to reach for the cross-vendor cross-check, and where the canonical homes are. Derives from the kit's real structure so it does not go stale. Use when asked "how do I use coding-mastermind / the kit" or "what does coding-mastermind give me."

Code Gen 0 2d ago

planning-and-task-breakdown

by MGallo-Code

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

Auth 0 2d ago

source-driven-development

by MGallo-Code

Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

Processing 0 2d ago

coding-mastermind-invariant

by MGallo-Code

Mints NEW invariants for a repo's INVARIANTS.md registry, then drafts and revert-tests the enforcer that guards each. Two modes - discover (mine git + GitHub history for recurring problems that have no registry row yet, ranked by recurrence) and add (scaffold one named invariant directly). Proposes the row AND the backing CI check/hook; never auto-edits or auto-commits. Use when asked to "add an invariant", "what invariant should we add", "turn this recurring bug into a gate", or "mine our history for things worth enforcing". Distinct from coding-mastermind-audit (which maintains EXISTING rows) and coding-mastermind-init (which scaffolds a whole repo).

Code Review 0 2d ago

test-driven-development

by MGallo-Code

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

Design 0 2d ago

debugging-and-error-recovery

by MGallo-Code

Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.

Debugging 0 2d ago

documentation-and-adrs

by MGallo-Code

Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Comments 0 2d ago