← all publishers

Background-Craft

@background-craft source repo

Report this profile Claim this profile

• 10 skills
• 0 followers
• 6 hours ago last updated

1. ▌
   Go · background-craft

   Implement a Hydrant issue end-to-end — fetch context, set up the branch, plan, build, verify, and commit. Use when the user asks for `/go`, says "go HYD-123", "implement HYD-123", or wants implementation started on a specific issue. The "do the work" command in the lifecycle.
   0
   installs
2. ▌
   Nail · background-craft

   Tighten an existing Hydrant issue — reduce ambiguity, ground vague references against the user's codebase, and extract inline metadata (dependencies, labels, milestone, priority) into proper Hydrant fields. Use when the user asks for `/nail`, says "nail HYD-123", or wants an issue made precise before implementation.
   0
   installs
3. ▌
   Prep · background-craft

   Assess Hydrant issue readiness before implementation — fetch issue and codebase context, identify and de-risk unknowns, and decide if the issue can move to `/go`. Use when the user asks for `/prep`, says "prep HYD-123", or wants a readiness gate before coding.
   0
   installs
4. ▌
   Yeet · background-craft

   Ship a Hydrant branch — detect where you are in the commit→push→PR→merge→cleanup pipeline and pick up from there. Use when the user asks for `/yeet`, says "ship this", "yeet HYD-123", or wants the current branch fully delivered and `main` cleaned up.
   0
   installs
5. ▌
   Align · background-craft

   Scan the user's codebase, ask up to five clarifying questions, and write a fenced Alignment block into AGENTS.md that the Hydrant lifecycle skills (`/go`, `/prep`, `/preflight`, `/yeet`) read for stack-specific behavior. Use when the user asks for `/align`, says "align hydrant-skills", wants the lifecycle skills tuned to this codebase's conventions, or runs the install for the first time.
   0
   installs
6. ▌
   Setup · background-craft

   First-run install for hydrant-skills — detect the active harness, configure the hosted Hydrant MCP server, write a fenced "Hydrant lifecycle workflow" section into AGENTS.md (and CLAUDE.md if Claude Code), and verify the connection by calling `mcp__hydrant__list_spaces`. Use when the user asks for `/setup`, says "set up hydrant-skills", "install Hydrant MCP", "wire up Hydrant", or runs the toolkit for the first time after `npx skills add`.
   0
   installs
7. ▌
   Refine · background-craft

   Refine a rough or underspecified Hydrant issue into an implementable one — fill missing scope, acceptance criteria, edge cases, and metadata so it can move to `/prep` without further coaching. Use when the user asks for `/refine`, says "refine HYD-123", or wants an issue cleaned up before implementation.
   0
   installs
8. ▌
   Cleanup · background-craft

   Sync `main` and prune stale local branches after merging Hydrant work. Use when the user asks for `/cleanup`, says "clean up after merge", "tidy my branches", or wants `main` resynced and merged-but-still-local branches removed. The post-`yeet` housekeeping pass.
   0
   installs
9. ▌
   Preflight · background-craft

   Run the pre-PR quality gate on a Hydrant branch — lint, build, tests, coverage assessment, acceptance-criteria check, dependency-graph verification, production-safety review, and adversarial review. Use when the user asks for `/preflight`, says "preflight HYD-123", or wants final validation before shipping.
   0
   installs
10. ▌
    Create Issue · background-craft

    Turn a rough request into an unambiguous, implementation-ready Hydrant issue grounded in the codebase and live project state, with all metadata routed to proper fields. Use when the user asks for `/create-issue`, says "make a ticket for X", or wants a request shaped into an issue ready for `/prep` and `/go` without an intermediate `/refine` or `/nail` pass.
    0
    installs