What is workflow-best-practices?

Development guidance for a required work process: start an issue, write code, run tests, commit, deploy, check production, and close the issue. The workflow-enforcer service checks that these steps are followed.

Use it when your project requires a fixed path from an issue through coding, testing, deployment, and verification.

It keeps work tracked, requires tests before commits, and adds a production check after deployment.

How scarter4work/workflow-compliance-enforcer configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to scarter4work/workflow-compliance-enforcer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/scarter4work/workflow-compliance-enforcer/main/.claude/skills/workflow-best-practices/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/scarter4work/workflow-compliance-enforcer

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/scarter4work/workflow-compliance-enforcer/workflow-best-practices/github.svg)](https://agentmods.dev/skills/scarter4work/workflow-compliance-enforcer/workflow-best-practices)

Your own site

<a href="https://agentmods.dev/skills/scarter4work/workflow-compliance-enforcer/workflow-best-practices"><img src="https://agentmods.dev/badge/skills/scarter4work/workflow-compliance-enforcer/workflow-best-practices/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/scarter4work/workflow-compliance-enforcer/workflow-best-practices"><img src="https://agentmods.dev/badge/skills/scarter4work/workflow-compliance-enforcer/workflow-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,897 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01897
Opus 5	$0.00000	$0.00949
Sonnet 5	$0.00000	$0.00379
Haiku 4.5	$0.00000	$0.00190

Measured 7d ago against content hash 8f57e8d8b87a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

workflow-best-practices scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

workflow_verify_prod({ test_command: "curl https://myapp.com/health" })

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

workflow-compliance-enforcer — 100% identical, 0 lines differ

.claude/skills/workflow-best-practices/SKILL.md · 350 lines

How it starts

The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow Best Practices

Overview

This skill provides context and examples for the enforced development workflow. The workflow is physically enforced by the workflow-enforcer MCP server.

The Mandatory Workflow

You MUST follow this exact sequence:

Start Issue → workflow_start_issue
Write Code → Use normal file tools
Run Tests → workflow_run_tests
Commit → workflow_commit (only after tests pass)
Deploy → workflow_deploy
Verify Production → workflow_verify_prod
Close Issue → workflow_close_issue

Why This Workflow Exists

Why Start with an Issue?

Ensures all work is tracked
Provides context for code reviewers
Links commits to requirements
Enables better project management

Why Run Tests Before Commit?

Prevents broken code from entering the repository
Catches regressions early
Maintains code quality standards
Saves time debugging later

Why Verify in Production?

Integration tests don't catch everything
Real-world data behaves differently
Network, latency, and scaling issues appear in prod
Confirms the actual problem is solved

Common Scenarios

Scenario 1: Tests Fail

You: workflow_run_tests
MCP: ❌ Tests failed! [output]

CORRECT RESPONSE:
1. Analyze the test failure
2. Fix the code
3. Run workflow_run_tests again
4. DO NOT try to commit

WRONG RESPONSE:
- "I'll commit anyway and fix it later" ❌
- Trying to use git commit directly ❌

Scenario 2: Forgot to Start Issue

You: *writes code*
You: workflow_run_tests
MCP: ❌ No active issue. Use workflow_start_issue first.

CORRECT RESPONSE:
1. Use workflow_start_issue with the issue number
2. Then proceed with testing

This happens because you skipped step 1.

Scenario 3: Production Tests Fail

You: workflow_verify_prod
MCP: ❌ Production tests failed!

CORRECT RESPONSE:
1. Investigate the prod failure
2. Fix the code locally
3. Run workflow_run_tests
4. workflow_commit with fix
5. workflow_deploy again
6. workflow_verify_prod again

The issue remains open until prod tests pass.

Read the full file on GitHub · 350 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 350 lines · 0 tokens per session scan A 8f57e8d8b87a

Subscribe to this mod's changes

workflow-best-practices is a skill published in the GitHub repository scarter4work/workflow-compliance-enforcer (0 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,897 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens

workflow-compliance-enforcer: Skill for Claude Code