agentleFS
cryptofish7cryptofish7/claude-skills/skills/setup-workflow/SKILL.md

setup-workflow

Skill1 starsChanged 9 months agoMITView on GitHub

Set up the autonomous post-task workflow for a project. Injects the standard development pipeline into CLAUDE.md and installs all required skills and agents (docs-consolidator, ci-cd-pipeline, smoke-test, bug-bash-update, code-reviewer, debugger). Use at the start of a new project. Triggers on "setup workflow", "init workflow", "add workflow", or "set up project workflow".

5 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use tdd.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 10 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Skills: Check that SKILL.md exists at the live path.

    line 29
  2. Very specific:

    Agents: Check that the agent .md file exists at the live path.

    line 30
  3. Distinctive:

    If all dependencies are present, proceed to Phase 2.

    line 34
  4. Distinctive:

    If any are missing, report which ones and stop:

    line 36
  5. Distinctive:

    Search for the project's CLAUDE.md file:

    line 45
  6. Distinctive:

    Check for CLAUDE.md in the project root

    line 46
  7. Very specific:

    Check if root CLAUDE.md is a symlink to docs/CLAUDE.md

    line 48
  8. Distinctive:

    If found, note the path. If not found, note that a new one will be created.

    line 50
  9. Very specific:

    Check if a ## Workflow section already exists

    line 56
  10. Very specific:

    Read references/workflow-template.md — this is the canonical workflow content.

    line 61
  11. Very specific:

    If a ## Quality Standards section already exists: Do not inject a duplicate.

    line 67
  12. Distinctive:

    If no CLAUDE.md exists: Create a new CLAUDE.md in the project root with this structure:

    line 69
  13. Distinctive:

    Read the updated CLAUDE.md

    line 95
  14. Distinctive:

    Never modify any section of CLAUDE.md outside the Workflow section (unless creating a new file)

    line 102
  15. Distinctive:

    If auto-detecting commands for a new CLAUDE.md, prefer reading the project's config files over guessing

    line 104
  16. Distinctive:

    If a dependency is missing, tell the user to install it rather than attempting to create it

    line 105

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Setup Workflow

Install the autonomous post-task development pipeline into a project's CLAUDE.md. All dependency skills and agents must be installed before running this skill.

Dependencies

This workflow requires 6 tools:

DependencyTypeLive path
docs-consolidatorSkill~/.claude/skills/docs-consolidator/SKILL.md
ci-cd-pipelineSkill~/.claude/skills/ci-cd-pipeline/SKILL.md
smoke-testSkill~/.claude/skills/smoke-test/SKILL.md
bug-bash-updateSkill~/.claude/skills/bug-bash-update/SKILL.md
code-reviewerAgent~/.claude/agents/code-reviewer.md
debuggerAgent~/.claude/agents/debugger.md

Workflow

Phase 1: Check dependencies

For each dependency in the table above, check if the live file exists:

  1. Skills: Check that SKILL.md exists at the live path.
  2. Agents: Check that the agent .md file exists at the live path.
  3. ci-cd-pipeline references: Also check this additional file:
    • ~/.claude/skills/ci-cd-pipeline/references/deploy-prerequisites.md

If all dependencies are present, proceed to Phase 2.

If any are missing, report which ones and stop:

Missing dependencies:
- [dependency name]: expected at [path]
Install the missing skills/agents before running setup-workflow.

Phase 2: Detect CLAUDE.md

Search for the project's CLAUDE.md file:

  1. Check for CLAUDE.md in the project root
  2. Check for docs/CLAUDE.md
  3. Check if root CLAUDE.md is a symlink to docs/CLAUDE.md

If found, note the path. If not found, note that a new one will be created.

Phase 3: Read current state

If CLAUDE.md exists:

  1. Read it fully
  2. Check if a ## Workflow section already exists
  3. Note the line range of the existing Workflow section (from ## Workflow to the next ## heading or end of file)

Phase 4: Inject workflow

Read references/workflow-template.md — this is the canonical workflow content.

If a Workflow section exists: Replace it (from ## Workflow up to but not including the next --- or ## heading) with the content of workflow-template.md.

If CLAUDE.md exists but has no Workflow section: Insert the workflow content after the first heading block (title + any introductory text before the first ---).

If a ## Quality Standards section already exists: Do not inject a duplicate. Only inject the Quality Standards section (from the template) when creating a new CLAUDE.md or when no such section exists.

If no CLAUDE.md exists: Create a new CLAUDE.md in the project root with this structure:

# CLAUDE.md
## Project — Development Guide

This file provides context for Claude Code sessions working on this project.

---

[workflow-template.md content here]

---

## Commands

[Auto-detect from pyproject.toml / package.json / Makefile / Cargo.toml and list the project's lint, format, typecheck, and test commands]

---

## Mistakes to Avoid

*Claude: After any correction, add a rule here. Be specific.*

Phase 5: Verify

  1. Read the updated CLAUDE.md
  2. Confirm the Workflow section contains the full pipeline
  3. Confirm no other sections were accidentally modified
  4. Report a summary of all changes made

Guidelines

  • Never modify any section of CLAUDE.md outside the Workflow section (unless creating a new file)
  • The workflow template in references/workflow-template.md is the single source of truth
  • If auto-detecting commands for a new CLAUDE.md, prefer reading the project's config files over guessing
  • If a dependency is missing, tell the user to install it rather than attempting to create it

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.