agentleFS
Sign inStart free
dmzoneilldmzoneill/skills/dev-workflow-orchestrator/SKILL.md

dev-workflow-orchestrator

Skill2 starsChanged 19 days agoApache-2.0View on GitHub

High-level entry point for development workflows. Routes to start work, check deploy readiness, prepare MR, monitor pipelines, standup, or handle review. Use when user says "dev workflow" or "orchestrate".

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    check: Run local lint/tests, check_ci_health — deploy readiness

    line 31
  2. Very specific:

    Check for "no such host", "connection refused" → suggest vpn_connect()

    line 39
  3. Distinctive:

    Check for "unauthorized" → suggest credential refresh

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Dev Workflow Orchestrator

Routes common developer tasks to appropriate skills.

Inputs

InputTypeRequiredPurpose
actionstringyes"start", "check", "prepare_mr", "monitor", "standup", "review"
issue_keystringnoJira key (required for start, check, prepare_mr, review)
repostringnoRepository path

Workflow

1. Load Persona

  • persona_load("developer")

2. Route Action

  • Validate action in ["start", "check", "prepare_mr", "monitor", "standup", "review"]

3. Execute by Action

  • start: skill_run("start_work", '{"issue_key": "..."}') — create branch, Jira context
  • check: Run local lint/tests, check_ci_health — deploy readiness
  • prepare_mr: skill_run("create_mr", '{"issue_key": "..."}') — prepare merge request
  • monitor: gitlab_ci_status, pipeline status
  • standup: skill_run("standup_summary", "{}")
  • review: skill_run("check_mr_feedback", ...), handle review feedback

4. Detect Failures

  • Check for "no such host", "connection refused" → suggest vpn_connect()
  • Check for "unauthorized" → suggest credential refresh

5. Learn from Failures

  • learn_tool_fix(...) if patterns detected

6. Log Session

  • memory_session_log("Dev workflow: {action}", "issue=... success=...")

Output

Report with action result and next-step guide.

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.

Check your setup, free