smithery/NickCrew

dev-workflows

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

Installation

$ npx skills add smithery/NickCrew --skill dev-workflows

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/NickCrew · top by installs.

npx skills add smithery/NickCrew

Browse all from smithery/NickCrew

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,752 B
  • docs SUMMARY.md 182 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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