Headless multihost backbone for coding agents. Durable sessions, one JSON contract, your own tooling on top.
Drive the Pohunek CLI safely from an agent session with discovery, explicit targeting, JSON state reads, event subscriptions, bounded send-and-wait loops, and operator-first safety boundaries.
The operator hands over one issue and expects it back **merged, verified, and closed** â not a question, not a partial state. This skill chains the existing loop skills (`github-workflow` â `milestone` â `gates` â `pr-handoff` â `merge-advance`) and adds what they leave to the operator: th
Run the pohunek CI gate set locally and report the results honestly. Use before declaring any Rust change done, when a branch must be verified as building, or whenever a run of the repository gate set is requested. This is the shared verification block the milestone, milestone-review, merge-advance, and release skills all rely on.
Commit the current milestone unsigned, merge its slice stack into main bottom-up, delete the branches and prune the worktree, then update the milestone's issue and project status. Use when the user asks to land a finished milestone locally.
Turn a finished, gate-green milestone into a stack of small sequential PRs (one per slice branch, unsigned commits, bottom-up), each described from the milestone's audit evidence, then update the milestone's issue. Use when the user asks for a PR for a branch, or after a milestone-build harness run reports all DoD items met with the gates green.
Wraps `scripts/release` and the `Release` GitHub Actions workflow (`.github/workflows/release.yml`). Do the version bump through the script â never hand-edit `Cargo.toml`/`Cargo.lock` versions or hand-craft the tag.
Auto-indexed from zajca/pohunek
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.