playbooks

home / skills / nickcrew / claude-cortex / dev-workflows

dev-workflows skill

/skills/dev-workflows

This skill guides repeatable build, test, and DX improvements with diagnostics, safe execution, and clear follow-ups.

npx playbooks add skill nickcrew/claude-cortex --skill dev-workflows

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.4 KB
---
name: dev-workflows
description: Use when running builds, executing tests, or improving developer experience workflows - provides structured guidance for build/test execution and DX improvement.
---

# 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

| Task | Load reference |
| --- | --- |
| Build workflows | `skills/dev-workflows/references/build.md` |
| Test workflows | `skills/dev-workflows/references/test.md` |
| DX improvements | `skills/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

Overview

This skill helps teams run builds, execute tests, and improve developer experience workflows in a repeatable, reliable way. It emphasizes safe execution, clear diagnostics, and concrete next steps so problems are resolved quickly and documented for the team. Use it to standardize workflow execution and surface actionable follow-ups.

How this skill works

Pick a workflow type—build, test, or DX—and load the matching guidance for checks, commands, and expected outputs. Execute the workflow with monitoring to capture logs and diagnostics, then apply fixes or improvements and re-run verification steps. The skill produces an execution summary with status, errors, and suggested follow-ups to drive remediation and documentation.

When to use it

  • Running builds or diagnosing build failures in CI or locally
  • Executing test suites and analyzing failing tests with captured output
  • Improving onboarding, developer tooling, or documentation for DX
  • Triaging regressions where environment or workflow drift is suspected
  • Preparing targeted fixes and follow-up tasks after automated runs

Best practices

  • Always run baseline environment checks before executing workflows
  • Capture full logs and failing test outputs for reproducible triage
  • Document any workflow or tooling changes and their expected impact
  • Apply fixes in small, reversible steps and re-run verification
  • Record clear next steps and owners when follow-ups are required

Example use cases

  • A broken CI build: run the build workflow, collect diagnostics, fix dependency or config issues, verify, and document the cause
  • A flaky test suite: execute focused test workflows with logging, isolate the flakiness, add guards or retries, and update test guidance
  • Onboarding improvement: evaluate developer setup steps, streamline commands, add checks to catch common mistakes, and publish updated docs
  • Local repro of a production failure: mirror the CI environment, run targeted tests, capture artifacts, and hand off a concise execution summary

FAQ

Should I use this skill for full release preparation?

No. This skill targets build/test/DX workflows. Use a dedicated release-prep process for full releases.

What outputs should I always include after a run?

Include a concise execution summary with status, key errors, captured logs or failing output, and clear next steps with owners.