Skip to content
Back to skills

Dev Workflows

ASecurity

Use when running builds, executing tests, or improving developer experience workflows - provides structured guidance for build/test execution and DX improvement.

  • 37 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added February 7, 2026
code-quality

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned February 10, 2026

npx -y skills add NickCrew/claude-cortex --skill dev-workflows --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dev Workflows?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Dev Workflows
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nickcrew-dev-workflows/badge)](https://www.skillsdirectory.com/skills/nickcrew-dev-workflows)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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

Files in this skill

  • SKILL.md1.4 KB
  • references/build.md4.3 KB
  • references/dx.md2.6 KB
  • references/test.md4.4 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.