mimukit

mimukit/skills

Instructions file CodexOpenCode

AGENTS.md instructions for mimukit/skills, covering agents.md, skill naming: the kit convention, descriptions, the two loads and information hierarchy.

mimukit/skills

Skill Claude CodeCodex

Run a groomed ready GitHub issue through the whole build span unattended, covering worktree, implement, commit, review, fix, QA plan, and open PR, so one issue reaches a reviewable PR with no human at the keyboard. Use when the user says "run issue #N unattended" or "work the ready issues while I'm away". It starts…

mimukit/skills

Skill Claude CodeCodex

Create a git commit with a Conventional Commits message derived from the actual diff, then push it to origin. Use when the user asks to commit changes, says "commit this", runs "/commitkit", or wants a well-formed commit message written for staged work, even if they don't spell out the format.

mimukit/skills

Skill Claude CodeCodex

Chase a symptom to its true cause: reproduce it, shrink it, write falsifiable hypotheses, and prove the cause by toggling the symptom on and off, then hand over a failing reproduction instead of a fix. Use when the user says "debug this", "why is this failing", "find the root cause", "what's causing this bug", "this…

mimukit/skills

Skill Claude CodeCodex

Derive a project's design system from the UI it already ships and keep it true as the code moves, producing a spec-compliant DESIGN.md at the repo root, validated by the official linter. Use when the user says "write a DESIGN.md", "document our design system", "extract our design tokens", "our design system is out of…

mimukit/skills

Skill Claude CodeCodex

Maintain a project's domain model as a consented byproduct of design work: a CONTEXT.md glossary of the ubiquitous language and docs/adr/ decision records. Use when a domain term needs pinning down, when a hard-to-reverse trade-off decision gets settled, when the user says "write an ADR" or "update the glossary", or…

mimukit/skills

Skill Claude CodeCodex

The shared git layer every other skill borrows: where a worktree lives and what it's called, how to create/adopt/tear one down, which branch is the base, whether to rebase or merge, how to sync a feature branch with its base and force-push it, how to sweep merged worktrees and branches away, how to recover work that…

mimukit/skills

Skill Claude CodeCodex

Grill the user relentlessly about any idea, plan, or design, a round of unblocked decisions at a time, each with a recommended answer, until you both share the same picture. Use when the user wants to stress-test or pressure-test an idea, says "grill me", "grill this plan", "poke holes in this", "interrogate my…

mimukit/skills

Skill Claude CodeCodex

Compact the current conversation into a handoff document another agent or session can pick up cold: goal, state, next steps, key artifacts by reference, and constraints. Explicit invocation only, because auto-triggering is disabled so a session compaction never fires mid-work. Use when you deliberately run…

mimukit/skills

Skill Claude CodeCodex

Strip the tells of AI-generated writing from prose so it reads like a person wrote it. Use when asked to humanize text, remove AI-isms, make writing sound less like ChatGPT, edit out "AI slop," or review a draft for robotic phrasing without rewriting it. Covers em-dash overuse, puffery, filler, and the AI vocabulary…

mimukit/skills

Skill Claude CodeCodex

Think an idea through across many sessions, with one ideas repo holding a folder per idea, a jotpad for the thoughts that have none, one idea open at a time, and nothing written to disk until you ask for it. Use when the user says "capture this idea", "I just had an idea", "jot this down", "random thought", "promote…

mimukit/skills

Skill Claude CodeCodex

Implement a plan, spec, or issue into working code, picking straight-through vs TDD mode by precedence (prompt → CLAUDE.md → repo habit → ask), then running the repo's test + build gate before declaring done. Use when the user says "implement this plan", "implement #42", "do this TDD", or "apply these review…

mimukit/skills

Skill Claude CodeCodex

Own the GitHub issue lifecycle in five modes: create issues from a plan or description, start a ready issue into its own worktree, close one out once its PR merges, sync PR↔issue links after merge, and triage the tracker for lifecycle and priority gaps. Use when the user says "create issues from this plan", "file an…

mimukit/skills

Skill Claude CodeCodex

Take an open GitHub PR and make it merge-ready on your machine (worktree, base-branch sync, project running, review pack), then merge it once you say so, or service review feedback on a PR you authored. Use when you say "pull PR #34 down so I can test it", "merge PR #34", "address the review comments on my PR", or "my…

mimukit/skills

Skill Claude CodeCodex

Name a project to a naming convention you already use, then prove the name is free on the domain, npm, and GitHub before you commit to it. Use when the user says "name this project", "what should I call this", "give me project name ideas", "come up with a name for X", "is taken", "check if this name is available", or…

mimukit/skills

Skill Claude CodeCodex

Keep the Orca desktop app's workspace list honest about the git worktrees your workflow actually creates: link each one to its issue, keep its status current, and clean out the ones whose work already merged. Use when the user says "orcakit", "clean up my orca workspaces", "my Orca sidebar is full of finished work"…

mimukit/skills

Skill Claude CodeCodex

Push the git worktrees your workflow actually creates into Paseo's workspace registry, because Paseo discovers nothing on its own and prunes nothing on its own. Use when the user says "paseokit", "sync my worktrees to paseo", "sync all my projects to paseo", "my paseo sidebar is missing worktrees", "paseo doesn't show…

mimukit/skills

Skill Claude CodeCodex

Turn a rough feature or change into a structured plan document (docs/plans/plan- -YYYY-MM-DD.md) before any code: brainstorm the approach, settle the big decisions, and write a plan that can be hardened and turned into issues. Use when the user says "plan this feature" or "brainstorm a plan/PRD/spec", the front of the…

mimukit/skills

Skill Claude CodeCodex

Draft and open a GitHub pull request from your branch, with title, summary, and test plan written from the actual commits and diff, then created with the gh CLI, embedding verifykit proof artifacts inline when a bundle is present. Use when the user asks to open a PR, says "create a pull request", "raise a PR", "submit…

mimukit/skills

Skill Claude CodeCodex

Sharpen the prompt before you send it, whether the one-shot instruction you're about to hand a coding agent or the system prompt your application ships. Use when the user says "optimize this prompt", "what's wrong with this prompt", "write or rewrite the system prompt my app ships", or "/promptkit".

mimukit/skills

Skill Claude CodeCodex

Build throwaway code that answers a question, whether an interactive state model you can drive, a script that measures one thing, or competing UI mocks to choose between, then fold the answer into the decision and delete the code. Use when the user says "prototype this", "spike this", "does this state model hold up"…

mimukit/skills

Skill Claude CodeCodex

Generate a step-by-step manual QA and test plan for a feature just implemented, grounded in the actual code changes, and save it to docs/qa for a human to run. Use when a coding session wraps and you want to hand-test the result, or the user says "write a QA plan", "make a manual test plan", "how do I test this"…

mimukit/skills

Skill Claude CodeCodex

Survey an existing codebase for the structural change worth making, then rank the candidates, crown one, and write it up as a reviewable proposal. Use when the user says "where should I refactor", "this code is hard to change", or "audit the module boundaries". It proposes and never edits code.

mimukit/skills

Skill Claude CodeCodex

Cut a release from the Conventional Commits a repo already writes: derive the semver bump and a changelog from the commit range, bump the manifest, tag it, and publish a GitHub release, all behind a mandatory preview. Use when the user says "cut a release", "tag a version", "release this", "what's the next version"…