Validates and repairs an in-scope change, publishes its draft pull request, reconciles metadata and CI, and marks it ready for review. Use when asked to open, raise, or publish a pull request for the current change, or when the user runs /create-pr.
Prepares or publishes a release using the repository's established versioning and publication workflow. Use when asked to cut, prepare, or publish a release, when the user runs /create-release, or when milestone-rush hands off a milestone.
Establishes the actual cause of something observed by checking what really ran or loaded, trying to break each candidate explanation, and having the result reviewed in a fresh context before reporting it. Use before claiming a cause or proposing a fix for an observed failure, hang, leak, or unexpected agent behavior, when asked why something happened or what is causing it, or when the user runs /deep-dive.
Carries one feature, bug, issue, branch, or PR through verified delivery. Use when asked to deliver or ship a work item end to end, such as getting it merged or deployed, or when the user runs /deliver.
Provides deterministic, resumable GitHub transition waits used internally by delivery workflows. Use when another workflow must await CI, merge, tag, or release state without model heartbeats.
Develops a GitHub issue or idea until its requirements and fidelity criteria are verified. Use when asked to implement, build, or fix a described change or GitHub issue, or when the user runs /implement.
Installs, updates, or migrates project-local skills from their verified upstream source while preserving local ownership and pins. Use when asked to add, refresh, or migrate a project's local skills.
Autonomously completes a confirmed milestone by reconciling existing work, coordinating work-item delivery and the configured milestone release, and closing the verified milestone. Use when the user runs /milestone-rush or asks to complete one exact, confirmed milestone, including selecting it after /roadmap-review.
Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.
Reviews a roadmap from fresh project evidence and produces a verified, throughput-anchored version plan, with execution gated on confirmation. Use when reviewing a roadmap, planning releases, or sequencing a backlog.
Reviews a workstream and agrees process improvements, applying only the selected follow-up actions. Use when the user asks for, runs /run-retro, or accepts a retrospective.
Applies the user's engineering standards during substantial technical work: preserve scope, use current evidence, delegate independent parts, and complete authorized outcomes. Use during substantial implementation, debugging, refactoring, or multi-part delivery work.
Builds a read-only current-repository Kanban from live pull-request, CI, review, branch, and worktree evidence. Use when the user asks for a status report, PR board, review-readiness board, or local-work overview.
Tests observable behavior against explicit requirements through the real interface. Use when asked to test or verify that a change meets its specification or acceptance criteria, when the user runs /test-against-spec, or when a delivery workflow needs real-interface acceptance evidence.
Applies strict, runtime-aligned TypeScript conventions for compiler setup, types, modules, APIs, tests, and validation without imposing a frontend framework. Use when scaffolding, configuring, writing, reviewing, or upgrading TypeScript in web, service, CLI, library, or tooling projects.
Commits relevant changes, merges the remote base when needed, pushes the current pull-request branch, and refreshes stale PR metadata. Use when asked to update or push changes to an existing pull request, or when the user runs /update-pr.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.