Recurring Workflow to SKILL.md with Trigger, Steps and Verification

Claude Code interviews you briefly about a repeated workflow and writes a complete SKILL.md with a precise trigger description, steps, supporting files and a verification step.

You get: Working code with an explanation

More like this

Ready to use: no blanks to fill in.

The prompt

Installs to .agents/skills/recurring-workflow-to-skill-md-with-trigger-steps-and-verificati/

mkdir -p .agents/skills/recurring-workflow-to-skill-md-with-trigger-steps-and-verificati && curl -sL "https://prompts-gpt.com/prompts/recurring-workflow-to-skill-md-with-trigger-steps-and-verification/raw" -o .agents/skills/recurring-workflow-to-skill-md-with-trigger-steps-and-verificati/SKILL.md
SKILL.md
Preview
---
name: recurring-workflow-to-skill-md-with-trigger-steps-and-verificati
description: "Claude Code interviews you briefly about a repeated workflow and writes a complete SKILL.md with a precise trigger description, steps, supporting files and a verification step."
---

# Recurring Workflow to SKILL.md with Trigger, Steps and Verification

Claude Code interviews you briefly about a repeated workflow and writes a complete SKILL.md with a precise trigger description, steps, supporting files and a verification step.

## Prompt

```
You are an expert at writing Claude Code skills. First ask me two short questions: what recurring workflow I want to capture, and what a finished run looks like. Skim the repo for existing scripts, templates and .claude/skills so you reuse what exists. Then write the skill. Rules: 1) The frontmatter has a lowercase hyphenated name and a description that states what the skill does and the exact situations or phrases that should trigger it, plus a note on when not to use it. 2) Steps are numbered, imperative, and name the exact commands and files; keep the main file under 100 lines and move long reference material or templates into supporting files. 3) End with a verification step that runs a concrete command or check and says what a pass looks like. 4) Do not invent tools or paths you did not find; mark assumptions. Output: assumptions, the folder layout, each file in its own code block labeled with its path, a three-case test plan for triggering the skill, then risks and next actions.
```

## Usage Notes

Use it right after you notice you have explained the same process to Claude Code more than twice. Be ready to describe the workflow in a sentence or two when asked.

Example output

AI-written example
<!-- ASSUMPTIONS -->
Interview answers (simulated):
- Workflow: cutting a patch/minor release of our npm package `@acme/csv-kit`.
- Finished run: version bumped, CHANGELOG.md updated, tests green, annotated tag `vX.Y.Z` created locally, release PR open. Nothing is published to npm by Claude.

Found in repo:
- package.json with scripts `test` and `build`
- CHANGELOG.md (Keep a Changelog format)
- scripts/release-notes.sh (prints commits since the last tag)
- No existing .claude/skills entries

Assumptions (verify before use):
- [ASSUMED] Default branch is `main`; releases go through a PR from `release/vX.Y.Z`.
- [ASSUMED] The `gh` CLI is installed and authenticated.
- [ASSUMED] Commits follow Conventional Commits.
- [ASSUMED] `scripts/release-notes.sh` accepts the previous tag as `$1`.
<!-- FOLDER LAYOUT -->
.claude/skills/cut-release/
├── SKILL.md
├── reference/
│   ├── changelog-entry-template.md
│   └── bump-rules.md
└── scripts/
    └── verify-release.sh      (new; written by this skill)
scripts/release-notes.sh       (existing; reused, not modified)
<!-- .claude/skills/cut-release/SKILL.md -->
---
name: cut-release
description: Cuts a new release of the npm package in this repo. Bumps the version, updates CHANGELOG.md from commits since the last tag, runs tests, creates a local git tag and opens a release PR. Use when the user says "cut a release", "ship a patch", "bump the version", "prepare v1.x" or "release notes and tag". Do NOT use for publishing to npm, for hotfixes on old branches, or for writing changelog text without releasing.
---

# Cut a release

## Steps

1. Confirm a clean state: run `git status --porcelain` and `git branch --show-current`. Stop if the tree is dirty or the branch is not `main`.
2. Run `git pull --ff-only origin main` and `git describe --tags --abbrev=0` to get the previous tag.
3. List changes with `bash scripts/release-notes.sh <previous-tag>`.
4. Choose the bump using `reference/bump-rules.md`. State the chosen version and the reason, then ask the user to confirm before editing anything.
5. Create the branch: `git switch -c release/v<new-version>`.
6. Run `npm version <new-version> --no-git-tag-version` to update package.json and the lockfile.
7. Add a new section at the top of `CHANGELOG.md` using `reference/changelog-entry-template.md`. Group entries under Added, Changed and Fixed. Drop commits of type `chore` and `ci`.
8. Run `npm test` and `
Generated from this prompt by AI. Your results will vary.

Tips and common edits

Use it right after you notice you have explained the same process to Claude Code more than twice. Be ready to describe the workflow in a sentence or two when asked.

Questions about this prompt

More in Claude Code

CLAUDE.md or AGENTS.md Audit: Cut, Rewrite as Checkable Rules, Move to Skills

Turns a pasted CLAUDE.md or AGENTS.md into a shorter file of verifiable rules and names which procedures belong in skills.

Conventional Commit and PR Description Writer Skill (SKILL.md)

A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.

Pre-Merge Code Review Checklist Skill (SKILL.md)

A save-ready SKILL.md that has your coding agent review a branch before merge: correctness, security, tests and migrations, with findings ranked by severity and no style nitpicks.

Write a SKILL.md From a Workflow You Keep Repeating

Interviews you about a task you do over and over, then writes a complete, save-ready SKILL.md with a trigger description, steps, output format and stop conditions.

Brand Voice Guard Skill That Checks Drafts Against VOICE.md (SKILL.md)

A SKILL.md that makes Claude write and edit in your brand's voice: it reads a VOICE.md in the project, or builds one from samples, then checks every draft against it.

Meeting Notes to Decisions and Action Items Skill (SKILL.md)

A SKILL.md that turns any meeting transcript or rough notes into a decision log, owner-and-date action items, open questions and a ready-to-send recap email.

Release Notes From Git Log Skill for Users and Developers (SKILL.md)

A SKILL.md that writes release notes from the commits between two tags, split into a plain-language section for users and a technical changelog for developers.

Spreadsheet and CSV Cleanup Report Skill (SKILL.md)

A SKILL.md that has your agent profile a messy CSV or spreadsheet, fix it in a copy with a script, and report every change so the cleaned data can be trusted.

Test-First Bug Fix Skill: Reproduce, Fix, Prove (SKILL.md)

A SKILL.md that forces your coding agent to reproduce a bug with a failing test before changing code, apply the smallest fix, and prove it with the test suite.

Agent Run Post-Mortem: Trace Root Cause and Prompt or Tool Fixes

Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.

Characterization Tests Before a Refactor

Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.

Checkpoint and Rollback Manager with Compensation Steps and Failure Injection Tests

Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.