niekcandaele
- 40 skills
- 0 followers
- 9 hours ago last updated
- ▌ QA · niekcandaelePragmatic QA engineer that evaluates test coverage quality, flags untested changes, and assesses whether tests provide real confidence — adapts expectations to codebase testing maturity
- ▌ Player · niekcandaeleImplementation skill for player-coach. Reads the plan, writes code and tests, and addresses verification feedback.
- ▌ To Spec · niekcandaeleTurn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
- ▌ Wizard · niekcandaele bundleGenerate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
- ▌
- ▌ Prototype · niekcandaele bundleBuild a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
- ▌ Wayfinder · niekcandaelePlan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
- ▌
- ▌ Verify · niekcandaeleRun comprehensive triage-first verification pipeline with specialized skills. Detects scope, discovers toolchain, triages files to relevant skills, runs static analysis, invokes review skills in parallel, exercises the app, and produces a unified report. Supports interactive, report-only, and auto-fix modes.
- ▌ Create Pr · niekcandaele bundleCreate or update a pull request or merge request with rich reviewer context, or perform one durable PR lifecycle operation for a caller: open a draft, append an append-only comment, mark it ready, or request review. Handles branch creation, commits, pushes, provider binding, labels, and inline review. Use whenever creating or updating a PR/MR; callers such as player-coach can supply implementation journey and friction context.
- ▌ Renovator · niekcandaele bundleSweep a repository's open dependency PRs (Renovate, Dependabot, or similar): tier each by risk, merge the trivial green ones, research and verify the rest, and leave one upserted comment per PR a maintainer can act on in under five minutes.
- ▌ Review Pr · niekcandaeleReview a pull/merge request by fetching PR details, checking CI, and running verification skills on the changes
- ▌ Grill Me · niekcandaele bundleGrilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
- ▌ To Tickets · niekcandaeleBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
- ▌
- ▌
- ▌ Rich Page · niekcandaele bundleGenerate a single self-contained HTML page that is genuinely visual AND interactive — charts, diagrams, motion, tabs, comparison toggles, click-to-expand, base64-inlined images, opinionated typography. Use whenever the user wants ANY rich visual artifact from arbitrary content: explainer, research write-up, PRD or spec page, pitch, internal one-pager, "make this less boring" rebuild, scroll-snap deck, landing-style summary, distilled report. Trigger phrasings: "make me a page about X", "turn this PDF/doc into something visual", "build me a deck/talk/pitch", "explain Y in a visual way", "make this readable", "give it some eye candy", "I want something I can show the team", "less boring version of this", "rebuild that page", "redo it with more visuals". Output is one .html file that renders identically when DM'd — CDN libraries (Tailwind, Chart.js, D3, GSAP, Mermaid, Lucide) load from stable jsdelivr/unpkg URLs; every image is base64-inlined. Not for plain Markdown docs (use technical-writer), not for code revi
- ▌ Reviewer · niekcandaeleComprehensive code reviewer combining design review, architecture, coherence, hardening, and security analysis
- ▌ Epic Runner · niekcandaele bundleWork an entire epic of tickets unattended — for each ticket: plan it, implement it, PR it into an epic branch, drive CI green, merge; then verify the assembled epic once and file follow-ups. Works with any tracker: GitHub, Jira, GitLab, or a markdown checklist. Use when the user hands over a batch of related issues and wants them worked through autonomously ("run this epic", "work through these tickets", "do the whole milestone"). For a single ticket where the work deserves an adversarial implement/review loop, use `player-coach` instead.
- ▌ Exerciser · niekcandaeleManual E2E tester that starts the app and exercises new features end-to-end
- ▌ Player Coach · niekcandaele bundleAdversarial cooperation loop for ONE ticket — player implements, verify reviews, every changed default turn is pushed to a draft PR, CI passes, and the PR is marked ready. Invoke only when the user explicitly asks for the player-coach loop. Do not use for an ordinary coding request. For a whole epic, use epic-runner instead.
- ▌ UX Reviewer · niekcandaeleUser experience specialist that evaluates all user-facing outputs for clarity and usability
- ▌ Release Notes · niekcandaeleGenerate user-facing release notes from technical change information (commits, PRs, diffs, branch comparisons, or raw text). Goes deep — follows commit references to PRs, issues, and bug reports to understand the full story behind each change, then produces narrative prose that communicates what changed and why it matters. Works with GitHub, GitLab, and Jira. Use this skill whenever the user asks for release notes, changelogs, "what's new" summaries, or wants to communicate changes to users, stakeholders, or customers — even if they just say "write up what changed" or "summarize the release."
- ▌ Debugger · niekcandaeleEvidence-based troubleshooting specialist that analyzes problems without fixing them
- ▌ Research · niekcandaele bundleMulti-source research specialist that investigates a topic, verifies claims across independent sources, and reports findings with dated citations. Use this whenever the user wants you to research, investigate, "look into", "dig into", "find out about", "get up to speed on", or "what's the latest on" something; to compare options ("X vs Y", "which is better"); or to map a landscape ("give me the lay of the land on Z"). Two depths: a normal request gives a fast cited report in chat; saying "deep research" (or passing --deep) runs a multi-phase investigation that fans out parallel sub-agents across the branches of the topic, synthesises them, and renders the result as a rich visual HTML page via the rich-page skill. Prefer this skill over answering research questions from memory — it verifies and cites instead of guessing. Not for reviewing code, summarising a single document you already have, or debugging a specific failure (use reviewer / technical-writer / debugger for those).
- ▌ Setup Engineer · niekcandaele bundleReconcile this repository toward the opinionated "golden state" for agentic local development — a per-repo dev CLI, a thin justfile surface, a generated port-offset env contract, a four-file engineer skill, thin CI, and a doctor invariant-enforcer. Run /setup-engineer whenever you want to set up, audit, or repair a repo's local-dev tooling: a fresh repo with nothing, a half-built repo with organic scripts that needs consolidating, or a finished repo you just want to verify still conforms.
- ▌
- ▌ Visual Verify · niekcandaeleVision-based visual QA reviewer — captures rendered output (live web pages, static HTML artifacts, PDFs) as screenshots, inspects them with a designer's eye for layout defects a human catches instantly, and normalizes findings into the verify pipeline format
- ▌ Codebase Design · niekcandaele bundleShared 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.
- ▌ Codex Reviewer · niekcandaeleIndependent second-opinion reviewer that shells out to the local Codex CLI for a broad code review, then normalizes findings into the verify pipeline format
- ▌ Comment Review · niekcandaeleComment-hygiene-only reviewer — flags ephemeral review-ID references, historical change-narration, stale comments, reviewer-appeasement, and redundant restating in the scoped diff, and normalizes findings into the verify pipeline format
- ▌ Technical Writer · niekcandaeleExpert technical documentation editor following Google and Grafana style guides for clear, developer-focused content
- ▌ Static Analysis · niekcandaeleStatic analysis runner that executes pre-discovered linter and type-checker commands on scoped files and reports findings
- ▌ Writing For Agents · niekcandaele bundleWriting documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
- ▌ Ubiquitous Language · niekcandaeleExtract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to CONTEXT.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
- ▌ Root Cause Coach · niekcandaeleAdversarial review coach for root cause analysis. Reviews reports with fresh eyes, runs verification commands to spot-check evidence claims, pushes hard on depth and rigor.
- ▌ Resolving Merge Conflicts · niekcandaeleUse when you need to resolve an in-progress git merge/rebase conflict.
- ▌ Root Cause Analysis · niekcandaeleRoot cause analysis — investigate directly in main context, then invoke a coach skill for adversarial review
- ▌ Improve Codebase Architecture · niekcandaeleFind deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
- ▌ Thermo Nuclear Code Quality Review · niekcandaeleRun an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.