Peter Bruinsma
Community@23min · Sweden
Building things that make systems understandable
Agent Skills by Peter Bruinsma
Showing 39 vetted skills indexed across 1 GitHub repositories.
23minwf-codebase-health
Guides module design and scores codebase health against structural principles with file:line evidence.
23minwf-review-code
Reviews a diff for correctness, tests, and conventions, producing a verdict with file:line findings.
23minwf-doc-lint
Detects broken code references, dead links, and structural drift in project documentation.
23minwf-structural-sweep
Detects dead code, duplication, and unconsumed data flow across a whole codebase.
23minwf-tdd-cycle
Guides red/green/refactor test-driven development with branch-coverage audits and vacuity checks.
23minwf-property-test
Generates property-based and metamorphic tests that assert invariants across fabricated inputs.
23minwf-patch
Executes a gated branch-and-merge ritual for small single-issue fixes and chores.
23minwf-vacuity
Audits existing test suites by mutating implementations and detecting tautological or weak assertions.
23minwf-rethink
Re-evaluates one code unit's design by reconstructing it from intent against pinned obligations.
23minaiwfx-plan-milestones
Decomposes an approved aiwf epic into sequenced, independently-shippable milestones with allocated ids.
23minaiwfx-whiteboard
Synthesizes open planning-tree items into a tiered landscape, recommended sequence, and decision fork.
23minaiwfx-handoff
Generates a paste-ready compaction handoff block summarizing volatile session state for /compact.
23minaiwfx-record-decision
Records project decisions as ADR or D-NNNN entities via the aiwf CLI.
23minaiwfx-release
Tags a semver release with CHANGELOG updates and gated git pushes after an aiwf epic closes.
23minaiwfx-plan-epic
Scopes and documents a new aiwf epic with allocated id and spec template.
23minaiwfx-record-gap
Records defects as aiwf gap entities with reproduced claims and independent review.
23minaiwfx-start-milestone
Starts an aiwf milestone with preflight checks, branch setup, and TDD-driven implementation.
23minaiwfx-wrap-epic
Closes an aiwf epic by verifying milestones, scaffolding a wrap artefact, and merging the epic branch with trailered commits.
23minaiwfx-wrap-milestone
Closes an aiwf milestone by verifying ACs, running reviews, and preparing the wrap commit.
23minaiwfx-start-epic
Activates an aiwf epic through preflight checks, sovereign promotion, and branch creation.
23minaiwf-list
Filters planning-tree entities by kind, status, parent, area, and priority via aiwf list.
23minaiwf-history
Queries git log commit trailers to reconstruct the lifecycle timeline of an aiwf entity.
23minaiwf-contract
Manages contract entities, validator bindings, and schema verification workflows in aiwf repositories.
23minaiwf-set-priority
Sets or clears priority levels on gap and decision entities via atomic commits.
Frequently Asked Questions About Peter Bruinsma
FAQPage SchemaWhat tasks can I perform with 23min's aiwf skills?▼
You can plan epics and milestones, run red/green/refactor TDD cycles with branch-coverage audits, review diffs with blocking/non-blocking verdicts, lint documentation trees for broken references, record gaps and ADRs, sweep dead code, and tag semver releases — all gated behind explicit human approval for commits and pushes.
Who are these skills designed for?▼
Software engineers and technical leads managing structured, spec-driven development. They suit teams that track work as versioned planning-tree entities (epics, milestones, gaps, decisions, contracts) and want enforced provenance, status transitions, and audit trails recorded through git commit trailers.
What are the prerequisites for using these skills?▼
Most aiwf-prefixed skills require the aiwf binary installed and a repository initialized with the aiwf planning tree. Git is required throughout, since entity state, history, and provenance ride on structured commit trailers. The wf- prefixed code-health skills are stack-agnostic and need no additional runtime.
How do the skills handle commits and destructive actions?▼
Commits, pushes, merges, releases, and agent delegations require explicit human approval. Sovereign acts like status promotion or check-finding exemptions require a named human/ actor with a written reason, recorded as an auditable git commit carrying aiwf-verb, aiwf-actor, and aiwf-reason trailers.
How do the testing skills ensure test quality?▼
wf-tdd-cycle enforces red/green/refactor per acceptance criterion with a hard branch-coverage audit. wf-vacuity adversarially breaks the implementation to confirm tests actually fail, flagging tautological assertions. wf-property-test converts invariants into generative property or metamorphic tests for parsers, ledgers, and state machines.