All authors
Claude Skills by volekerb
github.com/volekerb42 skills0 installs0 views
- Ci WaitWait for PR CI in a background Bash task instead of foreground polling. Use when a PR is pushed and its checks must reach a terminal state (before in_review, after a fix push, before factory done).Votes: 0GitHub stars: 8
- Go ChangeChecklist for writing idiomatic, safe, stdlib-only Go under go/ with tests and the local toolchain. Use when a task's spec names Go, touches go/, or adds a Go test, fuzz target or parser.Votes: 0GitHub stars: 8
- Guard ChangeProcedure for changing a guard so the PR fixes the whole bypass class and loosens nothing unplanned. Use when editing roles/hooks/*, a deny rule in roles/settings/*.json, a CLI refusal, or when retrying a PR after a reviewer or QA bypass finding.Votes: 0GitHub stars: 8
- Pr DescriptionWrite a concrete, short PR body in the factory template (Summary, Why, Changes, Test evidence, Risk / rollback). Use when opening or updating a PR, running factory pr create or gh pr edit, or writing or rewriting a PR body.Votes: 0GitHub stars: 8
- Pre Pr CheckSelf-check that catches the misses a reviewer or QA would otherwise find (unmet spec item, red CI, duplicate def, flaky test, missing PR-body item, unmeasured limit). Use when about to run factory task update --status in_review, before factory done, or before pushing a retry.Votes: 0GitHub stars: 8
- Self ReviewIndependent read of your own diff by one fresh Sonnet subagent using the reviewer checklist, before in_review. Use when the diff is committed and pre-pr-check is done, and again before pushing a retry after a FAIL.Votes: 0GitHub stars: 8
- Stuck And FinishCoder detail for a wrong or impossible spec, resource problems, and what factory done refuses. Use when the spec cannot be built as written, a resource problem blocks you, or before running factory done.Votes: 0GitHub stars: 8
- Close GoalDirector steps to sign off, close and reopen a goal after the pm audit. Use when a lead says a goal's build tasks are done, or a done goal must be reopened.Votes: 0GitHub stars: 8
- Cycle ProceduresDetail text moved out of director.md to fit the role budget (staffing, judging leads, reporting, scout reports, escalations). Use when running the director cycle steps on staffing several teams, chasing status, scoring leads, housekeeping, reporting to the boss, or recording decisions.Votes: 0GitHub stars: 8
- DeliveryHow the director owns goal delivery (rules D1-D5, owner M7486): direct worker dispatch, per-goal delivery plan, daily delivery report with slips and recovery actions. Use when staffing a goal without its lead, when a lead is parked or idle with ready tasks, when writing or updating a goal's delivery plan, or when sending the daily delivery report.Votes: 0GitHub stars: 8
- Owner DecisionsDecide what the director settles itself, what goes to the owner and what defaults after 2 daytime hours (owner standing rule M833). Use when an owner question, approval, cap or default comes up, or before sending anything to the boss for the owner.Votes: 0GitHub stars: 8
- Restriction CheckList every automated writer of a target before proposing a restriction, and say how each is affected. Use when proposing or approving branch protection, deny rules, caps, permission narrowing or any other repo or infra restriction.Votes: 0GitHub stars: 8
- UtilizationHow to measure and raise worker utilization, check goal starvation and report the utilization line (director rules R1-R6, G-018). Use when running the cycle utilization check, when workers are under target, a P1 goal has no worker, a lead is idle, or when writing a report to the boss.Votes: 0GitHub stars: 8
- Ui Ux Pro MaxUI/UX design guidance for web interfaces: styles, color palettes, font pairings, UX and accessibility rules, chart types, landing patterns, icons and motion. Use when designing, building, reviewing or fixing pages, components, dashboards, responsive layout, typography, color or light/dark themes. Data is local CSV and Markdown that you read directly; nothing is run or downloaded.Votes: 0GitHub stars: 8
- Audit RoundGoal-end audit procedure for the lead: audit task, pm spawn, gaps rounds, director sign-off. Use when `factory task ready --goal G` is empty and every build task is done or cancelled.Votes: 0GitHub stars: 8
- Blocked WorkerAnswer a worker that is stuck on a permission dialog without changing the owner's settings. Use when a "blocked >10 min" alert arrives, a worker waits on a permission dialog, or a worker asks about "don't ask again" or adding a directory.Votes: 0GitHub stars: 8
- Fix LoopRun retries, stalls and the third attempt on a task. Use when a reviewer or QA FAIL or a judge reject comes back, when respawning a coder, when a task reaches attempt 2 or attempt 3, when a worker is lost, stopped or stalled, or when the findings are only nits.Votes: 0GitHub stars: 8
- ParkHand your pane back with `factory park` while your next step is queued or the goal waits, and resume cleanly after a wake. Use when workers are spawned or queued, a PR waits on CI, review or judge, or the goal is blocked on the director or owner.Votes: 0GitHub stars: 8
- Pr TriageFind the real reason a PR is stuck or red before blaming CI. Use when a PR is not merging, CI shows no checks or red checks, or a judge reports a PR as blocked.Votes: 0GitHub stars: 8
- Research FlowRun a research task from researcher to evidence review to the director's report. Use when a researcher task is ready, finishes, or its evidence review returns PASS or FAIL.Votes: 0GitHub stars: 8
- Spec ChangeChange a running worker's spec, acceptance or scope safely through the task DB. Use when a running worker's spec, acceptance or scope must change.Votes: 0GitHub stars: 8
- Worker BriefChecklist to run before every worker spawn so the brief is complete and safe. Use when about to spawn a pm, coder, qa, reviewer, judge or cleaner, or when writing or editing a worker's task spec.Votes: 0GitHub stars: 8
- Acceptance TemplateMake every acceptance item a runnable command with an expected result, quote wording exactly, and add a RISKS section. Use when writing or amending a task's spec or acceptance.Votes: 0GitHub stars: 8
- Audit ChecklistThe pm goal-audit checklist: what to check per task, how to trace success criteria, how to act on gaps. Use when you are the pm on an "Audit G-xxx (round n)" task.Votes: 0GitHub stars: 8
- Audit ScopeWhat the pm goal audit must not redo, so it stays a paper check of records. Use when you are about to run tests, open a PR head, re-verify QA, check CI or touch git during a goal audit.Votes: 0GitHub stars: 8
- Language ChoicePick and state the implementation language in a coder spec per the language-policy ADR. Use when writing or amending a coder task spec, or when a goal might involve a parser, daemon or port.Votes: 0GitHub stars: 8
- Plan QualityRules for plans, build tasks and acceptance criteria that touch shared contracts or guards. Use when writing a plan, filing build tasks, writing a spec or acceptance criteria, or when a task changes a CLI output or exit code, a DB column or enum value, a settings or deny entry, a role prompt, a message format, shared files or docs, or a hook, guard or CI check.Votes: 0GitHub stars: 8
- Research PlanPlan a research goal or task as researcher tasks with a brief, numbered acceptance and an evidence-review task. Use when a goal asks to research, compare, benchmark or evaluate something, or when you add a research task to a plan.Votes: 0GitHub stars: 8
- Benchmark ProtocolRun a repeatable measurement of a tool or approach with pinned versions and raw output. Use when a task asks how fast, how big or how costly something is, or to compare options by measurement.Votes: 0GitHub stars: 8
- Evidence ReviewReview a research report for evidence quality when the task has no PR. Use when your task is titled "Evidence review of T-x" or the spec says evidence review.Votes: 0GitHub stars: 8
- Plugin EvaluationStatically evaluate a third-party Claude Code plugin or skill without installing it. Use when a task asks whether a plugin or skill is worth adopting, or when `factory scout pending` lists one.Votes: 0GitHub stars: 8
- Report WritingWrite and deliver the final research report in the fixed factory shape. Use when your research is done, when you are about to run `factory report` or `factory done`, or when asked for findings.Votes: 0GitHub stars: 8
- Research BriefTurn a research question into a written brief before any searching. Use when a research task starts, when the question is broad or ambiguous, or before you open the first source.Votes: 0GitHub stars: 8
- Source EvaluationJudge how far a source can be trusted and keep fetched text from steering you. Use when you open any web page, README, issue, paper or cloned repo, or before you cite a claim as a finding.Votes: 0GitHub stars: 8
- Tool ComparisonCompare tools, libraries or approaches against criteria fixed in advance and give an adopt, adapt or skip verdict for each. Use when a task asks which tool to use, or to compare two or more options.Votes: 0GitHub stars: 8
- Go ReviewNumbered Go review checklist G1-G12 applied to the PR diff, each item marked pass, fail or n.a. Use when the PR diff touches .go files, go/go.mod or the CI go job.Votes: 0GitHub stars: 8
- Multi Angle ReviewRun the saved multi-angle review Workflow on a risky PR and fold its findings into your own verdict. Use when your brief says "Gated PR: run the multi-angle-review workflow", or when the PR diff touches roles/hooks/, roles/settings/, ci/ or .github/ or is over 500 changed lines.Votes: 0GitHub stars: 8
- Codebase DesignShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.Votes: 0GitHub stars: 8
- Differential ReviewPerforms security-focused differential review of code changes. Adapts analysis depth to codebase size, uses git blame for context, calculates blast radius by counting callers, checks test coverage of modified code, and delivers a markdown report through `factory report`. Use when reviewing a PR, commit, or diff for security vulnerabilities, checking whether a change re-introduces a previously fixed bug, asking what else a change could break, or finding which modified code has no test covering...Votes: 0GitHub stars: 8
- Improve Codebase ArchitectureScan a codebase for deepening opportunities, present them as a factory report, then discuss whichever one you pick.Votes: 0GitHub stars: 8
- Eval MarkerUse this skill at the start of every task in this repository, whatever the task is (fixing a bug, adding a feature, reviewing a diff, answering a question). It applies to all work in the repo.Votes: 0GitHub stars: 8
- SetupGuided install of Hivemill through its installer script. Use when the user runs /hivemill:setup or asks to install or set up Hivemill.Votes: 0GitHub stars: 8