Skills in this repository
SkillsMP has collected 118 skills from asermax/claude-plugins. Open a skill to review its source and details.
asermax/claude-pluginsShowing 40 of 118 collected skills.
Commits the changes in the repository as conventional commits, grouping related files and confirming the grouping with the user before anything is committed. Use when the user asks to commit, or when another mahou skill reaches its commit step.
Implements a change whose design and test design are settled the way mahou:implement does, but writes each repository's code test first. Per repository, a tester subagent writes the failing tests and validates each round, an implementer subagent writes the…
Turns a settled design and its test-design trees into the tracker's task list: proposes new tasks, reshapes stale ones, drops superseded ones, and writes them through whatever mechanism the project declares, whether Linear, GitHub issues, or a local markdown…
Brings a branch up to date with its base by fetching, rebasing, resolving, and verifying, then reports what moved. Never pushes.
Use when user explicitly requests to coordinate with other Claude Code agents, join an agent chat, or communicate across multiple repositories/projects
Finds the holes in a problem and solution definition and fills them with questions, working a design tree in rounds until nothing is left assumed. Stays at the level of behavior and decisions, never implementation. Use after the user has explored a problem…
Create conventional commits with automatic semantic version bumps for this plugin marketplace and the affected plugin(s). Use this skill whenever the user asks to "commit", "commit my changes", "make a commit", "bump versions and commit", "ship these…
Traces what an already-written change reaches. Fans out a tracer per changed element and reports only the places where behavior changes for someone. Use after code is written, before it is reviewed or merged.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include…
Take one quest and see it through in a single session — claim it, get onto the right branch, read it in full, present the work and settle what its record leaves open, solve it by its kind, and close it out. Use when the user wants to work the next thing on an…
Build something already designed, together with the user, then verify it and offer to commit. Use when a design is agreed and the work is ready to write, or when another skill needs the shared build discipline.
Load first when working with any zenku skill. Carries the vocabulary, the two rules, how to find the project's vault and conventions, and the habits for writing into it.
Lay out the current shape so the user can settle a new one — which modules exist, where the seams are, how data flows, and what earlier quests already decided. Use when the user wants to design a feature or a module, work out an interface, decide where a…
Talk something through with the user relentlessly, round by round, until you reach a shared understanding. Use when the user wants their thinking stress-tested, says to grill or press or challenge them, or when another skill needs a decision settled by the…
Seed an Obsidian vault the project then owns, and re-run it later to add a folder, a template or a base.
Analyze uncommitted changes and create grouped conventional commits.
Write something into the project's quest log in a few seconds — a bug, a chunk of work, a half-formed idea — without deciding anything about it. Use when the user says to note this down, add it to the backlog, capture this, or remember this for later, or when…
Get everything worth keeping out of a session before it ends — decided work into the quest log, findings about how something works into a note, and anything learned about how we work into the project's own conventions. Use at the end of any zenku session, or…
Write or update a durable note in the project's vault explaining how one part of the system works, following the project's own writing charter and templates. Use when the user wants something documented, a mechanism written up, a note brought back in line…
Build the thing — turn cleared ground into a shape and a set of slices, then land them one per session.
Close a quest out once its answer exists — write the answer on it, set its status, gist it into the adventure's solved index, and clear it from every blocked_by list that named it. Use when a question has just been answered or a slice has just been built, or…
Build throwaway code to answer a design question — does this state model hold up, does this API behave, is this fast enough, what should this look like. Use when the user wants to sanity-check an approach before committing to it, or when another skill needs a…
End an effort and clear it away — close out whatever is still open, carry out anything worth keeping, remove the spike worktree, and delete the effort's records. Use when an adventure has shipped or stopped being worth continuing, when a loose quest has just…
Travel a journey — work on something whose shape is not clear yet, mapping what stands in the way and clearing it one question per session, without building.
Investigate a question against high-trust primary sources and capture the findings in the project's vault. Use when the user wants a topic researched, docs or API facts gathered, reading legwork delegated, or when another skill needs a fact settled before a…
Load when working with any katachi framework command. Provides workflow principles, status tracking conventions, and decision guidance. This skill establishes the collaborative context for all framework operations.
Implement a delta following its plan
Parse and analyze personal financial transaction CSV exports to calculate account totals and generate detailed breakdowns. Use when the user asks to analyze transaction data, generate financial summaries, calculate account balances, or review spending from…
Interacts with live Hunk diff review sessions via CLI. Inspects review focus, navigates files and hunks, reloads session contents, and adds inline review comments. Use when the user has a Hunk session running or wants to review diffs interactively.
Use when starting any task in a project - keeps CLAUDE.md instruction file current with high-level project state, prompts for init if missing, adds reflection todo before work to ensure documentation stays updated
Creates a WorkCommission — bounded execution authority — from an active DecisionRecord. MANUAL ONLY: operator must explicitly type /h-commission. Never auto-invoked: commissions are execution-authority grants under Transformer Mandate. Runs freshness check,…
Compares 2+ candidate variants under parity discipline and returns a Pareto front (not a scalar winner) — declares the selection policy and parity plan BEFORE scoring, then scores each dimension across all variants in parallel to prevent anchoring bias. Make…
Records a binding DecisionRecord with full FPF DRR discipline — problem frame, decision/contract, rationale, consequences. MANUAL ONLY — the operator must explicitly type /h-decide. Never auto-invoked: per Transformer Mandate, the human principal records…
Diagnoses a failure with parallel rival-hypothesis testing — multiple read-only subagents test distinct explanations in parallel, then rank by evidence weight while keeping losing rivals visible so the root cause is found honestly, not just plausibly. Make…
Generates 3–5 genuinely distinct candidate solution variants for a framed problem — each variant differs in KIND (not just degree), carries an explicit weakest-link so weak options surface before implementation, and optionally marks stepping-stones that open…
Frames an engineering problem before any solution is explored — stabilizes the signal, names what is actually broken, declares acceptance criteria, and records a ProblemCard. Make sure to use this skill whenever the user proposes a refactor, rewrite,…
Records a micro-decision with rationale into the haft artifact graph — lighter than a full DecisionRecord but persisted so future sessions and conflict detection can surface it. Make sure to use this skill whenever the user says "remember that", "FYI for…
First-setup ceremony for a project that does not yet use haft — the agent reads the repository, drafts the minimum FPF carriers (target system, enabling system, term map) from observed code/docs, and presents them to the operator for review. The operator is…
Umbrella for FPF-style structured reasoning in a haft project. Carries the full reasoning palette in one place: framing, exploration, comparison, verification, notes, plus slideument patterns (NQD, Goldilocks, BLP, Scaling-Law Lens). Make sure to use this…
Project state dashboard for haft — read-only consolidation of active problems, pending decisions, refresh-due artifacts, open work commissions, recent notes, and module coverage. Make sure to use this skill whenever the user asks "where are we", "what's…