perkzen
UserLocal software factory: Linear ticket in, reviewed draft PR out. Runs the real Claude Code CLI on your subscription — no API keys, no containers, no custom auth.
Categories
Indexed Skills (17)
code-review
Two-axis review of the branch diff — Standards (repo coding standards plus a smell baseline) and Spec (.fabrika/work/spec.md) — then fix the findings and write the PR description. Use as the last stage before the PR opens.
codebase-design
Shared vocabulary for designing deep modules — module, interface, depth, seam, adapter, leverage, locality. Use when choosing where a seam goes, shaping a new interface, judging whether a module is shallow, or when another skill needs the deep-module terms.
configure
Read a repository's base branch, install command, checks and review bot, and propose the repo-specific parts of .fabrika/config.json. Use when the host asks for a configuration at `fabrika init`.
domain-modeling
Keep the project's domain model current while designing — resolve a term into CONTEXT.md, record a load-bearing decision as an ADR. Use when a spec, plan, or refactor names a concept the glossary lacks or contradicts, or settles a decision that is hard to reverse.
improve-codebase-architecture
Find deepening opportunities in the code a branch touched, record them in .fabrika/work/refactor.md, implement the Strong ones, explore the rest. Use after implementation, before security and code review.
security
Security review of the branch diff — find each weakness, fix or accept it, record it in .fabrika/work/security.md. Use after implementation, before code review.
tdd
Test-driven development — the red→green loop at pre-agreed seams, one commit per cycle. Use when implementing a plan slice, fixing a finding, or deepening a module.
to-spec
Turn a ticket into a spec at .fabrika/work/spec.md — problem, solution, user stories, seams, testing decisions, assumptions. Use at the start of a fabrika run, before planning.
to-tickets
Break a plan, spec, or the current conversation into tracer-bullet tickets as local markdown files that `fabrika run --file` accepts, each declaring what blocks it. Use when the user wants work split into tickets without touching the team's Linear.
branch-naming
Choose the type, slug, and preview flag for a ticket's branch. Use when the host asks for a branch name at the start of a run.
code-comments
How to comment code — why over what, plain language, one line inside a function, short doc comments on the exported interface. Use when writing or refactoring code, and as the comment rule in the review Standards axis.
fix-ci
Fix a failing pull-request check from its log. Use when the host reports checks that failed after a push.
grill-with-docs
Stress-test a plan without a human — walk its design tree in rounds, look up every fact, choose the recommended answer for every decision, record each one. Use when a plan needs grilling in an unattended run.
implement
Implement .fabrika/work/plan.md slice by slice through tdd, keeping the plan honest as you go. Use in the implement stage, after the plan and before the refactor pass.
plan
Turn .fabrika/work/spec.md into an ordered implementation plan at .fabrika/work/plan.md — vertical slices, each a test and the code that passes it — then grill it. Use after the spec, before implementing.
research
Investigate a question against primary sources and write the findings, with citations, to .fabrika/work/research/. Use when a spec, plan, or grill needs a fact about a library, API, or platform that the codebase cannot answer.
resolving-merge-conflicts
Resolve an in-progress git merge or rebase conflict and finish it, never abort. Use when the host reports conflicts after merging the base branch into this one.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.