itsOmidKarami
UserA local orchestrator for semi-autonomous agentic SDLC
Categories
Indexed Skills (27)
next
Use to run the next node of a Kraft Lite chain, and to resume one after a gate, a new session, or a cleared context - reads its whole state from disk, so it is always safe to call.
next
Use to run the next node of a Kraft Lite chain, and to resume one after a gate, a new session, or a cleared context - reads its whole state from disk, so it is always safe to call.
check
Use to see whether a repo's Kraft config has drifted from what this Kraft version ships - a hook stuck on its placeholder, a chain template missing a node, or a hook naming a plugin skill that isn't installed. Report-only unless the human asks for a fix.
onboard
Use to connect a new repo to Kraft - runs repo connect, admin init --repo and admin doctor in sequence, then verifies each step actually matches this repo's real setup before calling it done.
prepare
Use before starting non-trivial work - defines a spec (with review), optionally a plan (with review) if asked for one, then judges whether the work should happen inline in this session or be handed off to Kraft as a work item.
chain-review
Use when a work item has just had its implementation plan approved and the orchestrator asks whether the rest of the loaded chain still fits the work. Decides whether to add, lighten, or leave alone the not-yet-executed nodes, and emits a revised chain tail for human approval at the chain_finalized gate.
code-review
Use when the verify node asks for a review of the diff this work item has produced so far. Emits findings the fix loop reads, at severities that decide whether implementation runs again.
fix-loop-judge
Judge whether a fix loop's next cycle is worth spending, from the trend across the rounds already run.
gate-review
Use when Kraft asks whether a work item's gate needs a human. Reads the artifact the gate is about and reports approve, reject, fixed, or undecided — never clearing the gate itself.
mr-checks-repair
Read why a merge request's pipeline just failed, and repair what is fixable from here — starting with a missing label.
mr-metadata
Turn a finished branch into the merge request a reviewer can act on -- its title, labels, reviewers and the description.
plan
Turn an approved spec into an implementation plan of bite-sized, independently testable tasks.
security-review
Use when the verify node asks for a security review of a change that touches authentication, sessions, tokens, secrets, or permission checks. Emits findings the fix loop reads, at severities that decide whether implementation runs again.
spec
Turn a work item's brief into a design a human can approve or reject in one read.
gate
Use when a Kraft Lite chain is blocked at a gate - presents what the human must decide on, then records their approval or rejection.
init
Use once per repo before running a Kraft Lite chain - detects the test command and which installed skills can serve each chain hook, then writes a registry the human can edit.
start
Use when starting a new piece of work under Kraft Lite - materializes the chain's nodes as state records and runs the first node.
status
Use when someone needs to know where a Kraft work item has got to, or when a handed-off item should be watched until it finishes - the phase it is in, the node coming next, any gate it is waiting on, and a follow that ends by itself.
gate
Use when a Kraft Lite chain is blocked at a gate - presents what the human must decide on, then records their approval or rejection.
init
Use once per repo before running a Kraft Lite chain - detects the test command and which installed skills can serve each chain hook, then writes a registry the human can edit.
start
Use when starting a new piece of work under Kraft Lite - materializes the chain's nodes as state records and runs the first node.
status
Use to report where a Kraft Lite chain has got to - which node is live, what is blocking it, how many fix attempts are spent.
beads
Use when working in a repository that uses bd or Beads for durable project task tracking, issue dependencies, blocker management, multi-session handoff, or shared work memory. Trigger when the user asks to find ready work, claim or close tasks, create follow-up work, inspect blockers, recover project context, or choose between local planning and persistent project tracking.
board
Use when you need to know what Kraft is doing - what work is running, what is blocked or waiting on a person, the state of one work item, or whether a decision was already made in a spec or plan somewhere across the repos.
gates
Use when a Kraft work item needs a human decision or has gone wrong - approving or rejecting the gate it is waiting on, or pausing and resuming work that is heading in the wrong direction.
handoff
Use when work agreed in this session should be handed to Kraft instead of done here - after a spec and plan are settled, when the task is too big for this session, or when the current repo needs connecting to Kraft first.
review-brief
Turn a finished work item into the one page a human reads before approving the merge.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.