too-many-cooks

Prepares the current branch for CI by running the exact same steps locally and fixing issues. If CI is already failing, fetches the GH Actions logs first to diagnose. Use before pushing, when CI is red, or when the user says "fix ci".

Searches for duplicate code, duplicate tests, and dead code, then safely merges or removes them. Use when the user says "deduplicate", "find duplicates", "remove dead code", "DRY up", or "code dedup". Requires test coverage — refuses to touch untested code.

Audit spec/plan documents against the codebase. Ensures every spec section has implementing code, tests, and matching logic. Use when the user says "check specs", "spec audit", or "verify specs".

Creates a pull request with a well-structured description after verifying CI passes. Use when the user asks to submit, create, or open a pull request.

Upgrade all dependencies/packages to their latest versions for the detected language(s). Use when the user says "upgrade packages", "update dependencies", "bump versions", "update packages", or "upgrade deps".

Audits a website for SEO, AI search performance, structured data, mobile usability, broken links, and social media cards. Fixes issues found. Use when the user mentions "audit website", "SEO", "fix search ranking", "AI search", "structured data", "social media cards", or "website performance".

Build, test, and package the Too Many Cooks VSCode extension

Install development tools (mcp | extension | playwright)

Create a pull request for the too-many-cooks repo

Run tests for Too Many Cooks packages. Detects which packages to test based on changed files.

Build, serve, and test the Too Many Cooks documentation website (Eleventy + Playwright)