xkx121029/mcd-vibe-commit

A playful developer skill worth a few minutes on Programmer's Day, not a commit-message tool you would wire into a real workflow.

The problem

You are at a keyboard with a change staged and a commit message box waiting, and the boring option is another fix: update stuff. This project replaces that blank-box moment with a short personality quiz: answer three multiple-choice questions, get one of nine invented McDonald's personas and a four-letter code, and receive a themed commit line built from a menu item. If a token is available, it pulls real menu names from a McDonald's MCP endpoint; without one it uses a bundled mock menu, so the same answer flow completes. The result is a joke message plus a shareable persona card, not a message chosen for clarity or accuracy.

What's different

Scoring is deliberate rather than random: seven scored dimensions map answers to nine personas out of sixteen four-letter combinations, and each persona has four or five templates with a product name dropped into a slot. A set of twelve easter eggs reacts to specific inputs and dates (the 1024 date, the contest countdown, all-D answers), and repeat generation surfaces extra output. The MCP piece is read-only by design: three tools for menu, nutrition and nearby-store lookup, with ordering, coupons, address creation and payment explicitly refused in the tool whitelist.

That read-only posture is a sensible default, but it also means the real-menu integration adds flavor and nothing else—the mock path is described as producing equivalent output, so the token mostly buys you current product names. The project is explicitly labeled entertainment and not ordering advice. The bigger trade-off is that this is a presentation gimmick: the templates are fixed, so commit text reflects the quiz persona rather than the diff, and a team that adopted it routinely would get repetitive, uninformative history. Running it in a work repository is a choice about fun, not about improving commit quality.

Who should try it

Developers who want a Programmer's Day joke or a screenshot-ready persona result, team leads planning a one-off bit of fun, and people exploring what a minimal Agent Skill for a read-only MCP service looks like will get the intended value. Contest participants looking for a small reference structure for skill packaging are another fit. It is a poor fit for anyone who wants messages that describe changes, for CI or policy-enforced commit conventions, or for a tool that stays interesting after the novelty of nine personas runs out.

Requirements and limitations

Setup is to copy the directory into an Agent skills folder following the Agent Skills layout; scripts use only the Python 3.10+ standard library, so no third-party installation is needed. Real menu data requires a token from the McDonald's MCP platform, which can be supplied through conversational setup or a hand-edited .env; a separate MCP client configuration is also documented but optional. None of these is required to try it, because the mock menu covers the full quiz-to-commit flow.

After setup, the main thing to keep in mind is that the skill depends on an external, contest-scoped MCP service for live data, and the documented fallback is what keeps it usable when that service is unavailable or returns errors. The committed .env handling and the skills-directory dependency mean placement matters: it runs inside a compatible Agent, not as a standalone CLI. There is no license declared in the repository metadata even though the README states MIT, so verify that before redistributing or reusing code. The repository documentation is also partly contest logistics—deadlines and issue formatting—which will age quickly.

HotRepo's take

The dated record is thin: HotRepo first tracked the repository on 2026-10-24, its creation date, and the only board observation is a NEW-REPOSITORY board (not the overall Trending board) placement at #18 for Python with 156 total stars on 2026-10-25. With no comparable daily history, persistence cannot be judged from these signals. Treat it as a contest-period joke project and check the license file before reusing any of its structure.

Project source and documentation