workflow-mastery

Run parallel Claude Code workflows in git worktrees for .NET projects.

640|145|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill workflow-mastery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-mastery
Source: https://github.com/codewithmukesh/dotnet-claude-kit/tree/main/skills/workflow-mastery
Command: npx skills add https://github.com/codewithmukesh/dotnet-claude-kit --skill workflow-mastery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces friction and wasted time in .NET development by enabling parallel Claude sessions, repeatable verification, and automated formatting and permission handling so teams can deliver features faster and with fewer CI failures.

Core Features & Use Cases

  • Parallel worktrees & sessions: Run 3–5 Claude sessions in separate git worktrees to develop features, fix bugs, and write tests concurrently.
  • Plan then execute with verifiable results: Use plan mode to produce robust multi-file plans, then require automated verification by running dotnet build, dotnet test, diagnostics, and format checks before accepting changes.
  • Automation, hooks, and permissions: Add PostToolUse hooks to auto-format changes, pre-allow common dotnet commands to remove permission friction, and create reusable subagents for verification and code simplification.
  • Use Case: Scaffold a new API endpoint in one worktree, generate integration tests in a second, and run verification and diagnostics in a third to produce a production-ready change with minimal manual iteration.

Quick Start

Create a git worktree for your feature, open parallel Claude sessions, and ask one session to plan while another runs dotnet build and dotnet test to verify changes.

Frequently Asked Questions about workflow-mastery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run parallel Claude Code sessions for .NET development without conflicts?

Parallel .NET development uses git worktrees to isolate branches, allowing multiple Claude Code sessions to run concurrently without file conflicts. This setup enables simultaneous feature scaffolding, bug fixes, and test generation across isolated working directories.

Can I automate dotnet format checks after Claude Code modifies my project files?

Yes, PostToolUse hooks can be installed to automatically run dotnet format checks whenever Claude Code modifies project files. This automated formatting ensures code style compliance and reduces CI pipeline failures before changes are committed.

What's the best way to verify dotnet build and test results during AI-assisted coding?

The best way to verify dotnet build and test results is using a verification loop that automatically runs diagnostics, build checks, and test suites before accepting AI-generated code changes. This ensures automated validation catches errors during development.

Do I need to configure permissions for common dotnet commands in Claude Code?

Pre-allowing common dotnet commands removes permission friction during automated workflows. Configuring these permissions upfront enables Claude Code subagents to execute repeatable tasks like building, testing, and scaffolding without manual approval prompts.

Why does my dotnet CI pipeline fail after generating code with AI assistants?

CI pipelines often fail after AI code generation due to unformatted code or build errors. Implementing automated verification loops with PostToolUse hooks and subagents validates changes by running dotnet build and test before submission.

How to scaffold a .NET API endpoint and generate integration tests concurrently?

Scaffolding a .NET API endpoint and generating integration tests concurrently requires creating separate git worktrees for each task. Open parallel Claude Code sessions in each worktree to develop features and write tests simultaneously with isolated verification.