mcpField
D
dev-workflows

dev-workflows

github.com/nickcrewDevelopment6287 installsUpdated 17w ago
Repository

About dev-workflows

dev-workflows is a skill for developers who need repeatable build, test, and developer-experience workflows. It uses task-specific references and emphasizes monitoring, diagnostics, verification, and documented follow-ups.

Key features

  1. 01Build workflow guidance
  2. 02Test execution and failure analysis
  3. 03Developer experience improvements
  4. 04Task-specific reference files
  5. 05Diagnostics and outcome summaries

Use cases

  1. 01Running builds and diagnosing failures
  2. 02Executing tests and reviewing failures
  3. 03Improving onboarding and developer tooling

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nickcrew/claude-cortex --skill dev-workflows

After installing, type/dev-workflowsin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
build.md
dx.md
test.md

Details

From the project README

Dev Workflows

Overview

Unify build, test, and DX improvement workflows so they are repeatable and reliable. Focus on safe execution, clear diagnostics, and actionable follow-ups.

When to Use

  • Running builds or resolving build failures
  • Executing tests or analyzing test failures
  • Improving onboarding, tooling, or developer workflows

Avoid when:

  • The task is pure code implementation
  • A full release process is required (use release-prep)

Quick Reference

TaskLoad reference
Build workflowsskills/dev-workflows/references/build.md
Test workflowsskills/dev-workflows/references/test.md
DX improvementsskills/dev-workflows/references/dx.md

Workflow

  1. Select the workflow type: build, test, or DX.
  2. Load the matching reference file.
  3. Execute with monitoring and capture diagnostics.
  4. Apply fixes or improvements as needed.
  5. Verify outcomes and document next steps.

Output

  • Execution summary (status, errors, next steps)
  • Suggested follow-ups or improvements

Common Mistakes

  • Skipping baseline environment checks
  • Running tests without capturing failing output
  • Changing DX workflows without documenting impact

Comments

Markdown supported