All authors
Claude Skills by itsOmidKarami
github.com/itsOmidKarami27 skills0 installs0 views
- GatePresents a Kraft Lite gate to the human and records their answer with `approve` or `reject`, sending rejected work back to the node that needs redoing. Use when a Kraft Lite chain's state is `blocked` at a gate, or the human answers a gate.Votes: 0GitHub stars: 7
- InitWrites `.kraft-lite/registry.yaml`, which binds each hook of a Kraft Lite chain to an installed skill, an instruction, or the repo's own test and CI commands. Use when that file is missing or stale (a hook has no binding) in a repo about to run a chain; `kraft-lite:start` sends you here when it is missing.Votes: 0GitHub stars: 7
- NextRuns the next node of a Kraft Lite chain from its recorded state and reports the finished run's time and attempts per node. Use when continuing a chain: right after `kraft-lite:start`, after a gate answer, or in a new or cleared session. A chain blocked at a gate belongs to `kraft-lite:gate`; a read-only progress question belongs to `kraft-lite:status`.Votes: 0GitHub stars: 7
- StartCreates a new Kraft Lite chain for the work and hands it to the first node. Use when the human asks to begin new work under Kraft Lite; continuing an existing chain is `kraft-lite:next`.Votes: 0GitHub stars: 7
- StatusReports where a Kraft Lite chain has got to (its node, running or blocked at a gate, attempts spent) and, on request, what a finished run took. Use when asked where a Kraft Lite chain is, whether it is stuck, or how long it ran; `kraft-lite:next` continues a chain and `kraft-lite:gate` answers a gate.Votes: 0GitHub stars: 7
- BoardReads what Kraft is doing across work items: the board, and a cross-repo search of specs, plans and session summaries. Use when asked what work is running, blocked or waiting on a person, or whether a decision was already made in a spec or plan in another repo. One item's progress or a watch belongs to kraft:status, and a stopped item to kraft:triage.Votes: 0GitHub stars: 7
- CheckReports where a repo's Kraft config has drifted from what this Kraft version ships: chains that no longer resolve, nodes and capabilities the live config lacks, a missing setup command, skills a chain names that are not installed. Use after a Kraft upgrade or when chains or the library look stale; a server that is unhealthy is kraft:doctor.Votes: 0GitHub stars: 7
- DoctorDiagnoses an unhealthy Kraft server and applies the reload, restart or update its health check calls for. Use when the server seems unhealthy or unresponsive, work items are not being picked up, or an upgrade or config change needs applying. A repo that will not connect is kraft:onboard; a stopped work item is kraft:triage.Votes: 0GitHub stars: 7
- GatesApproves or rejects the gate a Kraft work item is waiting on, files and submits review threads, and pauses or resumes work. Use when a person has made the call at a gate, wants line comments sent, or wants running work stopped and restarted; kraft:review helps decide first, kraft:steer and kraft:triage cover redirecting and stopped items.Votes: 0GitHub stars: 7
- HandoffFiles work with Kraft as a paused work item, with any agreed spec and plan attached. Use when work settled in this session should be handed to Kraft instead of done here, or the task is too big for this session. It connects a repo Kraft has not seen; verifying that repo's test and setup commands belongs to kraft:onboard, the inline-or-Kraft decision to kraft:prepare.Votes: 0GitHub stars: 7
- OnboardConnects a repository to Kraft and verifies that its test and setup commands work in a fresh worktree. Use when a repo is not yet connected to Kraft, or a newly connected repo has not been verified. Config drift in an onboarded repo belongs to kraft:check, an unhealthy server to kraft:doctor.Votes: 0GitHub stars: 7
- PrepareWrites the spec for non-trivial work, then judges whether it runs inline in this session or is handed to Kraft. Use before starting work that needs a spec, or when unsure whether work belongs inline or in Kraft; kraft:handoff does the filing once that is decided.Votes: 0GitHub stars: 7
- ReviewReads the spec, plan or diff a Kraft work item's pending gate is about and recommends approving or rejecting it, with reasons, for the person to confirm. Use when an item is waiting at a gate and someone asks for a review or help deciding; kraft:gates owns the approve, reject and submit calls themselves.Votes: 0GitHub stars: 7
- StatusReports which phase a Kraft work item is in and what runs next, and watches it until it finishes. Use when someone asks where a work item has got to or wants a handed-off item watched; for why it stopped, use kraft:triage.Votes: 0GitHub stars: 7
- SteerRedirects a Kraft work item by revising its spec or plan before it starts, or by pausing and resuming it with a steer once it has. Use when a work item is heading the wrong way or its spec or plan needs revising; to find out why one stopped, use kraft:triage.Votes: 0GitHub stars: 7
- TriageDiagnoses why a Kraft work item stopped, failed or is stuck needing a person, and routes it to a retry, a raised cap or the right sibling skill. Use when someone asks why an item stopped or how to get it going again; a pending gate alone belongs to kraft:gates.Votes: 0GitHub stars: 7
- Chain ReviewDecides whether the nodes after the revision gate still fit the approved spec and plan, and writes a chain_revision change set: skip a node, add a library node, override effort or caps, or change nothing. Kraft runs it as the library's revise_chain task, right after the spec and plan are approved.Votes: 0GitHub stars: 7
- Code ReviewReviews the diff a work item has produced for defects its passing tests miss, and writes severity-ranked findings to the result file. Kraft runs it as the review task of a verification node, after the test step is green; use it when that task asks for a review of the change so far.Votes: 0GitHub stars: 7
- Fix Loop JudgeJudges whether a fix loop's next cycle is still worth spending, from the trend of findings across rounds and the budget used, and reports continue, stop_needs_human or stop_downgrade. Use when Kraft asks it after a fix loop's first cycle, before each further one; it neither reviews nor fixes code.Votes: 0GitHub stars: 7
- Gate ReviewReviews the document a gate is about and reports a verdict, so a person only sees the gates that need one. Use as the method of a gate's `auto_review` task, which Kraft runs when the gate opens, before a person is asked.Votes: 0GitHub stars: 7
- Mr Metadata RepairRepairs a merge request's metadata, such as a missing or wrong label or a missing description section, so its checks can pass. Kraft runs it as the on_failure repair of the merge request's CI wait, on every failure; it acts only when the failed job's trace names a label or a description section.Votes: 0GitHub stars: 7
- Mr MetadataWrites the title, labels, reviewers and description of the merge request Kraft opens from a finished branch, following the repository's own templates and rules. Use when Kraft is about to open that merge request, after the work is done and reviewed locally.Votes: 0GitHub stars: 7
- PlanWrites the implementation plan for a work item from its human-approved spec, as small independently reviewable tasks. Kraft runs it as the library's plan_author task, after the spec gate and before implementation. Use when a chain needs that plan written or revised.Votes: 0GitHub stars: 7
- Review BriefWrites the review brief a human reads at the final review gate before merge: what changed, what CI said, what the local review flagged, what was left out, what is uncertain. Use for the task that produces the review brief, which Kraft runs once the merge request is open and before that gate.Votes: 0GitHub stars: 7
- Security ReviewReviews the diff a work item has produced for authentication, session, token, secret and permission-check defects, and writes severity-ranked findings to the result file. Kraft runs it as an extra review task beside the general code review in a verification node. No shipped chain runs it: an operator adds it to the library and a chain, for changes that touch those areas.Votes: 0GitHub stars: 7
- SpecWrites the design spec for one work item from its brief, headless, for a human to approve or reject. Kraft runs it as the library's spec_author task, before the plan is written; use when a work item's brief needs a design before planning.Votes: 0GitHub stars: 7
- Work BriefWrites the work brief a human reads at the pre-draft gate to decide whether the locally finished work becomes a draft merge request. Use when a chain task produces the work_brief, after implementation, tests and local review and before any merge request is opened.Votes: 0GitHub stars: 7