kit-and-kaboodle

Automates Linear issue implementation through Playwright verification, Codex review, and PR creation.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mcmurrym/coding-agent-skills --skill kit-and-kaboodle-mcmurrym
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kit-and-kaboodle
Source: https://github.com/mcmurrym/coding-agent-skills/tree/main/agent-skills/kit-and-kaboodle
Command: npx skills add https://github.com/mcmurrym/coding-agent-skills --skill kit-and-kaboodle-mcmurrym

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Delivering a Linear issue end-to-end requires juggling branch setup, implementation, browser testing, code review, and PR creation by hand. This Skill orchestrates that entire gated workflow so an issue goes from kickoff to a verified, reviewed pull request without manual coordination between steps. ## Core Features & Use Cases - Gated end-to-end workflow: Starts from a Linear issue URL or key, runs implementation, and only proceeds when each stage passes. - Playwright browser verification: Writes ad-hoc Playwright tests from the issue's acceptance criteria, records video of the run, and iterates up to 15 fix attempts before stopping with structured failure output. - Codex code review with complexity gating: Filters review findings to changed code, measures cyclomatic complexity, auto-fixes low-complexity issues, and defers high-complexity findings as PR review comments. - Use Case: A developer pastes a Linear issue key and receives a PR containing the implemented change, an attached screen recording of the browser verification, and inline review comments for any risky findings. ## Quick Start Use the kit-and-kaboodle skill to take Linear issue CP-123 through implementation, browser verification, code review, and PR creation.

Frequently Asked Questions about kit-and-kaboodle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a Linear issue to pull request workflow?▼

Provide a Linear issue URL or key and the workflow fetches the issue context, creates a branch, implements the changes, verifies them in a browser with Playwright, runs a Codex code review, and opens a PR with the verification recording attached.

How does Playwright browser verification work in this workflow?▼

The workflow starts the dev server, writes an ad-hoc Playwright test from the issue's acceptance criteria, and runs it with video recording enabled. Failures trigger targeted code fixes and re-runs, looping up to 15 attempts before stopping.

What happens when the Codex code review finds issues?▼

Findings are filtered to code actually changed on the branch and validated as real issues. Low cyclomatic complexity findings are auto-fixed and re-verified, while high-complexity findings are left unfixed and added as PR review comments with suggested fixes.

What happens if Playwright verification keeps failing?▼

After 15 failed attempts the workflow stops, kills the dev server, pushes the current code, and does not create a PR. It returns structured failure info including the issue key, attempt count, last error, recording path, and an iteration log.

Does this workflow modify the Playwright test to make it pass?▼

No. The guardrails explicitly require fixing the underlying code rather than the test, unless the test itself is wrong. The 15-attempt limit is absolute and cannot be reset to work around failures.