Kieran Potts
Community@kieranpotts · Bristol, UK
Kieran Potts publishes a CC0-licensed collection of 30 skills covering the full software delivery lifecycle, from requirements discovery through Git operations, testing, and release.
Agent Skills by Kieran Potts
Showing 29 vetted skills indexed across 1 GitHub repositories.
research
Gather external sources on a topic and produce a cited research report.
commit
Compose and validate Git commit messages against a fixed type vocabulary and format.
design
Evaluate architectural options against nine design qualities and record one recommended decision per decision point.
proof
Proofread and conservatively edit prose files for spelling, grammar, and consistency.
validate
Evaluate working software against the originating user need and report prioritized specification gaps.
decide
Frame technical decisions and write them up as RFC records with alternatives and trade-offs.
branch
Creates and validates Git branch names under a trunk-based branching model.
discover
Elicit business requirements through structured interviews and produce a product requirements document.
resolve
Implements, verifies, and resolves open review comments on a pull request.
merge
Integrates work between Git branches using the merge strategy matching their branch types.
handoff
Writes an ephemeral handoff document summarizing session state for the next agent or human.
plan
Decompose an agreed design into ordered, independently shippable delivery steps.
reflect
Extract durable lessons from agent sessions and persist them to memory or convention files.
code
Implement one planned step test-first and commit it as a single reviewable diff.
style
Normalizes whitespace, wrapping, quoting, and ordering in code and text without changing behavior.
release
Cut release branches, apply annotated version tags, and ship build artifacts to registries.
triage
Verify and classify issue tracker reports, then recommend category and state labels.
diagnose
Diagnose bugs and performance regressions by testing ranked hypotheses against a reproducible feedback loop.
create-skill
Author and validate new agent skill directories with SKILL.md templates.
audit
Evaluate codebase architecture for modularity, coupling, and misplaced boundaries, then write an audit report.
elaborate
Interrogate a draft design through one-question-at-a-time interviews to resolve open decisions and ambiguities.
review
Audits a code diff against its specification and project standards, producing severity-labeled findings and a verdict.
fix
Repairs build, lint, and type-check failures with minimal verified changes.
spike
Write throwaway code to answer one falsifiable design question within a time-box.
Frequently Asked Questions About Kieran Potts
FAQPage SchemaWhat tasks can I perform using Kieran Potts's skills?▼
The 30 skills cover the full delivery lifecycle: requirements discovery and specification, architecture design and RFCs, test-first implementation, code review, refactoring, bug diagnosis, acceptance testing, Git branching, merging, committing, releasing, threat modeling, and session handoff.
Who are these skills designed for?▼
Software engineers, technical leads, and engineering agents working in disciplined, trunk-based development environments. They suit practitioners who separate concerns like design, planning, implementation, review, and release into distinct, well-gated steps.
What license and cost apply to these skills?▼
All skills are released under the CC0-1.0 public domain dedication, meaning they are free to use, modify, and redistribute for any purpose, including commercial use, with no attribution required.
What prerequisites and dependencies do the skills require?▼
Skills require combinations of Read, Write, Edit, Glob, and Grep file operations, plus Bash access to Git commands, test runners, formatters, linters, type-checkers, profilers, and issue tracker or review host CLIs. Some research-oriented skills also need WebSearch and WebFetch.
How do the skills handle Git branching and merging?▼
The branch skill names and creates branches under a trunk-based model with short-lived and epic branches, while the merge skill selects the correct integration strategy — rebase-then-fast-forward, squash merge, merge commit, or fast-forward — based on source and target branch types.