mimukit · Agent Skills
30 Skills avec une documentation substantielle et des sources vérifiées. Ouvrez une fiche pour lire les instructions originales et vérifier le paquet et son installation.
afkkit
Run a groomed ready GitHub issue through the whole build span unattended, covering worktree, implement, commit, QA plan, acceptance check, fix, 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 from a groomed issue; planning and grooming stay attended.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
dbkit
Model database schemas, write and check migrations so they run safely on a live database, find why a query is slow from its plan, and audit a schema and its migration history, in four modes: design, migrate, tune, and audit. Use when the user says "design the schema for …", "write a migration to …", "is this migration safe", "check this migration", "why is this query slow", "explain this query plan", "add an index for this query", or "audit our database schema".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
designkit
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 date", "audit our design tokens", "what colors does this project actually use", "sync DESIGN.md to our Tailwind theme", or "/designkit".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
gitkit
The shared git layer other skills borrow: the worktree path, name, and lifecycle, a worktree's declared setup and teardown, the base branch, rebase versus merge, branch sync, hotfix branches, merged-branch cleanup, lost-work recovery, and stacked branches. Use when the user says "make me a worktree for 42", "where's the worktree for this branch", "tear down this worktree", "set up this worktree", "make this worktree's dev database", "what's the base branch here", "should I rebase or merge", "syn
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
grillkit
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 design", or otherwise asks to interrogate a concept before committing to it, whether a rough idea, a plan file, an architecture, or a PR.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
handoffkit
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. Use when you deliberately run "/handoffkit" (optionally with a focus argument) to hand off work, write a handoff doc, or summarize the session for the next agent.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
ideakit
Think an idea through across many sessions, with one ideas repo holding a folder per idea, a jotpad for the thoughts that have none, and one idea open at a time. Use when the user says "jot this down", "promote that jot", "capture this idea", "let's think about the idea", "where do my ideas stand", "research for this idea", "is the idea worth building", "I'm dropping the idea", or runs "/ideakit".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
implementkit
Implement a plan, spec, or issue into working code in straight-through, tests-after, or TDD mode, then run the repo's test and build gate before declaring done. Use when the user says "implement this plan", "implement 42", "do this TDD", "build it, then add tests", "apply these review findings", or "make this failing test pass". It runs attended; the unattended issue-to-PR span is afkkit's.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
issuekit
Own the GitHub issue lifecycle in five modes: file issues from a plan, start a workable issue in its own worktree, close one once its PR merges, sync PR↔issue links and dependents after merge, and triage the tracker for label and title gaps and for done, duplicate, or obsolete issues. Use when the user says "create issues from this plan", "file an issue", "start issue 42", "close 42", "sync my issues", "triage the backlog", "set the priority on 42", "42 is grilled, mark it ready", "fix the title
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
mergekit
Take an open GitHub PR and set it up for review on your machine (worktree, 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 PR is red, fix the CI".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
namekit
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 "/namekit".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
orcakit
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", "which workspaces are stale", "link my worktrees to their issues", "remove the workspaces for merged issues", or "where should Orca put new worktrees".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
plankit
Turn a rough feature or change into a structured plan document (docs/plans/NNNN-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 plan → grill → file workflow.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
prkit
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 this for review", or "gh pr create", even if they don't spell out the title or body.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
promptkit
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".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
prototypekit
Build throwaway code that answers a question, whether an interactive state model you can drive, a script that measures one thing, or competing live UI variants to switch between in the app, 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", "is this library fast enough", or "try three live versions in the app". Not a demo generator and never production code.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
refactorkit
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".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
releasekit
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", "generate a changelog", "ship v2", or "/releasekit". It never publishes to a package registry and never moves a published tag.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
repokit
Configure a GitHub repo through gh in four modes: an inferred About description and topics, the workflow labels (issuekit's lifecycle and priority sets plus ai-review), a new-repo setup (house settings, baseline files, About, labels), and a docs/ renumbering into creation order. Use when the user says "set the repo description", "add topics", "provision the workflow labels", "set up this new repo", or "renumber the docs".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
researchkit
Research the credible options for a technical decision and recommend one (a tool, library, framework, architecture, or service) grounded in primary sources with cited, dated evidence. Use when the user asks "which should I use, A or B", "compare X and Y", "evaluate options for Z", "what's the best tool/library/service for …", "should we use X or Y", "research X before we build", or runs "/researchkit", the decision research that front-runs a plan.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
reviewkit
Review AI-agent-implemented code specifically, in four ordered passes (convention-fit, agent-slop signatures, requirement-completeness, correctness) against the working tree or the branch diff, findings ranked by severity and backed by quoted evidence. Use when the user says "review this code", "review my changes", or "check the agent's work" before commit or PR.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
seokit
Audit a web page, or crawl a whole site, for SEO and AEO gaps (crawlability, on-page, structured data, Core Web Vitals, AI-crawler access, answer extractability), then write a prioritized fix report and a long-term search and AI-visibility plan. Use when the user says "audit the SEO of " (including a localhost URL), "check SEO before I deploy", "crawl my site for SEO issues", "why isn't this page ranking", "is my site ready for AI search or ChatGPT", "check my robots.txt for AI bots", or "did my
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
skillkit
Create a new AI agent skill from scratch (kit-convention naming, drafting, trigger cases, live testing, publishing), or re-check an existing one after a change. Use when the user says "help me make a skill for X", runs "/skillkit", or says "I changed this skill, check it".
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.
statuskit
Survey a project read-only (working tree, issues and their priority, open PRs, unfiled plans, docs awaiting review) into a one-screen dashboard that crowns one finish-first next move routed to the kit that does it, saved by default as a throwaway snapshot under docs/status/. Use when you sit down at a project and ask "what should I do next" or "check project status"; add "no file" to skip the snapshot. It reads and recommends only; the crowned kit does the work.
- Installations / 1h
- 2
- GitHub Stars
- 2
- Mis à jour
- 11 nov.