Patrick Kollitsch
Community@davidsneighbour · Koh Samui, Thailand
Born 1975. Then things happened.
Agent Skills by Patrick Kollitsch
Showing 15 vetted skills indexed across 1 GitHub repositories.
davidsneighbourcommit
Write Git commit messages following the Conventional Commits specification.
davidsneighbourmanage-node-version-policy
Audits and updates Node.js and npm version declarations across a repository against the official release lifecycle.
davidsneighbourdependency-maintenance
Inspect, update, audit, and validate npm dependencies in single-package repositories and monorepos.
davidsneighbourlabels
Classify GitHub issues using a category:value label taxonomy and apply labels via GitHub CLI.
davidsneighbourforeman
Lists and routes requests to skills in the Clerkwork collection.
davidsneighbourdnbhq-configs
Audit and initialize DNBHQ shared configuration packages across repository tooling.
davidsneighbourproject-task-triage
Syncs local TODO.md notes with GitHub Issues and regenerates the PROJECT.md dashboard.
davidsneighbourbehaviour-spec
Create, review, and generate tests from strict Behaviour.spec.md specification files.
davidsneighbouragent-instructions-audit
Audit and optimise repository agent instruction architecture and context cost.
davidsneighbourresume-interrupted-work
Manages a project-root RESUME.md handoff file for resuming interrupted repository work.
davidsneighbourproject-state-report
Generates a project catch-up report from git history and GitHub issue and PR activity.
davidsneighbouragent-align
Creates and maintains AGENTS.md as the canonical repository agent instruction entry point.
davidsneighbourquality-gate-organisation
Standardizes npm script naming for repository quality-check commands.
davidsneighbourissues
Inspect, select, and implement GitHub issues through a structured issue-driven workflow.
davidsneighbourosv-scan
Scan npm dependencies for vulnerabilities with osv-scanner and triage findings via GitHub issues.
Frequently Asked Questions About Patrick Kollitsch
FAQPage SchemaWhat tasks can I automate using Patrick Kollitsch's Clerkwork skills?▼
Clerkwork skills handle Conventional Commits message drafting, npm dependency updates and audit fixes, OSV vulnerability scanning with issue filing, GitHub issue triage and labeling, Node.js version policy enforcement, project state reports with remote activity, and behaviour-spec-driven test generation.
Who are the Clerkwork skills designed for?▼
They target developers maintaining JavaScript/Node.js repositories and npm monorepos on GitHub who need consistent commit conventions, dependency hygiene, issue taxonomy enforcement, and agent instruction governance. Maintainers of single-package repos and multi-project local workspaces benefit most.
How do I invoke and route requests to Clerkwork skills?▼
Use the foreman skill as the entry point: run 'foreman overview' to list skills by category, narrow with 'foreman git' or 'foreman project', or route concrete requests like 'foreman audit packages' to the matching skill. Individual skills also trigger on natural phrases such as 'check status' or 'update Node versions'.
What prerequisites do the Clerkwork skills require?▼
Skills operate on Git repositories hosted on GitHub, with several requiring npm/package.json projects, osv-scanner for vulnerability checks, and GitHub Issues access. synchwork requires a local project set defined in .agents/skills/synchwork/config.json; resume-interrupted-work manages a project-root RESUME.md file.
Do Clerkwork skills modify my repository automatically?▼
Most are conservative by default. The agent-instructions-audit is non-mutating unless optimisation is explicitly requested, agent-align always asks for confirmation before changing files, and dependency-maintenance preserves unrelated work while optionally creating a conventional dependency-update commit after validation.