home / skills / athola / claude-night-market / development-workflow

This skill provides a modular development workflow hub that guides git, code review, testing, documentation, and deployment practices for Python projects.

npx playbooks add skill athola/claude-night-market --skill development-workflow

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

Files (7)
SKILL.md
5.6 KB
---
name: development-workflow
description: detailed development workflow with modular patterns for git, code review, testing, documentation, and deployment

Triggers: deployment, development, hub-and-spoke, modular, code
created_by: abstract-examples
tags: [development, workflow, modular, hub-and-spoke]
category: workflow
type: hub
estimated_tokens: 45
dependencies: []
companion_skills: []
modules:
  - git-workflow
  - code-review
  - testing-strategies
  - documentation-guidelines
  - deployment-procedures
tools:
  - setup-validator
  - workflow-checker
  - quality-metrics
---
## Table of Contents

- [Overview](#overview)
- [Available Modules](#available-modules)
- [Quick Start](#quick-start)
- [Usage Patterns](#usage-patterns)
- [For New Projects](#for-new-projects)
- [For Existing Projects](#for-existing-projects)
- [For Team Onboarding](#for-team-onboarding)
- [Integration Benefits](#integration-benefits)
- [Quality Assurance](#quality-assurance)
- [Customization](#customization)
- [Support and Resources](#support-and-resources)


# Development Workflow Hub

This modular skill provides a detailed framework for software development workflows. It's designed as a hub that coordinates specialized modules for different aspects of development.

## Overview

Get started quickly with this development workflow framework:

** Quick Start**: Set up repository structure and basic workflow in minutes
- Initialize with git-workflow module
- Add code-review process for team collaboration
- Implement testing strategies for quality assurance

**Progressive Learning**: Start simple, add complexity as needed
1. **Basic workflow** → git-workflow + code-review
2. **Quality focus** → add testing-strategies + documentation
3. **Production ready** → add deployment-procedures + monitoring

** Use Case-Based**: Jump directly to what you need
- New project? → Start with git-workflow
- Team scaling? → Focus on code-review + testing
- Production deployment? → Use deployment-procedures
- Documentation debt? → Apply documentation-guidelines

## Available Modules

This workflow includes these specialized modules:

- **[git-workflow](modules/git-workflow/)** - Repository setup, branching strategies, and daily git practices
- **[code-review](modules/code-review/)** - Pull request process, review guidelines, and quality standards
- **[testing-strategies](modules/testing-strategies/)** - Unit testing, integration testing, and E2E testing patterns
- **[documentation-guidelines](modules/documentation-guidelines/)** - Code documentation, API docs, and README standards
- **[deployment-procedures](modules/deployment-procedures/)** - CI/CD pipelines, environment setup, and monitoring

## Quick Start

To use this development workflow:

1. **Set up your development environment:**
   ```
   Use git-workflow module for repository initialization and branching setup
   ```
   **Verification:** Run the command with `--help` flag to verify availability.

2. **Follow the development cycle:**
   ```
   **Verification:** Run the command with `--help` flag to verify availability.
   git-workflow → code-review → testing-strategies → documentation-guidelines
   ```
   **Verification:** Run `pytest -v` to verify tests pass.

3. **Deploy and monitor:**
   ```
   **Verification:** Run the command with `--help` flag to verify availability.
   deployment-procedures module handles CI/CD and production monitoring
   ```
   **Verification:** Run the command with `--help` flag to verify availability.

## Usage Patterns

### For New Projects
Start with [git-workflow](modules/git-workflow/) to establish repository structure, then progress through modules as your project develops.

### For Existing Projects
Use individual modules to improve specific areas:
- Need better code reviews? → Use [code-review](modules/code-review/)
- Testing coverage issues? → Use [testing-strategies](modules/testing-strategies/)
- Deployment problems? → Use [deployment-procedures](modules/deployment-procedures/)

### For Team Onboarding
Guide new team members through the modules in order to establish consistent practices.

## Integration Benefits

This modular approach provides several advantages over monolithic workflows:

- **Token Efficiency**: Load only the modules you need (60% token reduction for most operations)
- **Focused Learning**: Each module concentrates on a specific development area
- **Flexible Implementation**: Adopt modules incrementally based on project needs
- **Team Specialization**: Different team members can focus on different modules

## Quality Assurance

Each module includes validation tools to validate best practices:
- Automated quality checks
- Performance benchmarks
- Security validations
- Documentation standards

Use the quality-metrics tool to assess your workflow implementation:
```bash
quality-metrics --workflow development-workflow --modules all
```
**Verification:** Run the command with `--help` flag to verify availability.

## Customization

This workflow is designed to be adaptable:
- Extend modules with project-specific practices
- Add custom tools to the scripts/ directory
- Configure module interactions for your team's needs
- Integrate with existing development tools and platforms

## Support and Resources

See the modules directory for detailed documentation on:
- Code review workflows
- Deployment procedures
- Documentation guidelines
- Git workflow patterns
- Testing strategies
## Troubleshooting

### Common Issues

**Command not found**
Ensure all dependencies are installed and in PATH

**Permission errors**
Check file permissions and run with appropriate privileges

**Unexpected behavior**
Enable verbose logging with `--verbose` flag

Overview

This skill provides a modular, detailed development workflow that covers git, code review, testing, documentation, and deployment. It acts as a hub of specialized modules so teams can adopt only the parts they need and scale practices progressively. The design favors incremental adoption: start small and add modules as projects and teams grow. The modules include repository setup, review standards, testing patterns, docs guidance, and CI/CD procedures.

How this skill works

The skill exposes distinct modules (git-workflow, code-review, testing-strategies, documentation-guidelines, deployment-procedures) that you enable independently or together. Each module supplies checklists, scripts, and validation tools to enforce standards, run quality metrics, and verify availability with simple --help and test commands. You integrate modules into your repository, adapt configuration files, and run validation commands like pytest and quality-metrics to confirm correct behavior. Modules are designed for incremental composition so you can swap or extend tools without rewriting the whole workflow.

When to use it

  • Initializing a new project to standardize branching, commit, and PR patterns
  • Onboarding a team to ensure consistent code review and testing practices
  • Improving test coverage or adding integration/E2E testing to an existing codebase
  • Preparing for production by adding CI/CD pipelines, environment setup, and monitoring
  • Reducing documentation debt with clear README and API doc standards

Best practices

  • Start with git-workflow to establish repository layout and branching strategy before adding other modules
  • Adopt code-review guidelines early and require PR checks to enforce quality gates
  • Use testing-strategies incrementally: unit tests first, then integration and E2E tests
  • Automate documentation generation and keep READMEs minimal but actionable
  • Configure CI/CD in deployment-procedures with staging, canary, or blue/green steps and include monitoring and rollback hooks

Example use cases

  • New Python microservice: initialize repo with git-workflow, add unit tests, and set CI for deployments
  • Growing team: introduce code-review module and enforce PR templates and reviewer rotation
  • Legacy project: apply testing-strategies to add coverage and use documentation-guidelines to reduce onboarding time
  • Production hardening: add deployment-procedures for automated pipelines, health checks, and alerting
  • Module-driven migration: adopt one module at a time (git-workflow → code-review → testing → docs → deployment) to limit disruption

FAQ

How do I verify a module is available in my environment?

Run the module command with the --help flag or run provided verification commands such as pytest -v and quality-metrics --workflow development-workflow --modules all.

Can I customize modules to match existing tools?

Yes. Modules are designed to be extended: add project-specific scripts, change config files, or integrate with your CI/CD and monitoring tools without replacing the entire workflow.