development-workflow
npx machina-cli add skill athola/claude-night-market/development-workflow --openclawTable of Contents
- Overview
- Available Modules
- Quick Start
- Usage Patterns
- For New Projects
- For Existing Projects
- For Team Onboarding
- Integration Benefits
- Quality Assurance
- Customization
- 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
- Basic workflow → git-workflow + code-review
- Quality focus → add testing-strategies + documentation
- 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 - Repository setup, branching strategies, and daily git practices
- code-review - Pull request process, review guidelines, and quality standards
- testing-strategies - Unit testing, integration testing, and E2E testing patterns
- documentation-guidelines - Code documentation, API docs, and README standards
- deployment-procedures - CI/CD pipelines, environment setup, and monitoring
Quick Start
To use this development workflow:
-
Set up your development environment:
Use git-workflow module for repository initialization and branching setupVerification: Run the command with
--helpflag to verify availability. -
Follow the development cycle:
**Verification:** Run the command with `--help` flag to verify availability. git-workflow → code-review → testing-strategies → documentation-guidelinesVerification: Run
pytest -vto verify tests pass. -
Deploy and monitor:
**Verification:** Run the command with `--help` flag to verify availability. deployment-procedures module handles CI/CD and production monitoringVerification: Run the command with
--helpflag to verify availability.
Usage Patterns
For New Projects
Start with 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
- Testing coverage issues? → Use testing-strategies
- Deployment problems? → Use 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:
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
Source
git clone https://github.com/athola/claude-night-market/blob/master/plugins/abstract/docs/examples/modular-skills/complete-skills/development-workflow/SKILL.mdView on GitHub Overview
Development Workflow Hub provides a modular framework that coordinates specialized modules for Git, code review, testing, documentation, and deployment. It helps teams start quickly and scale by composing proven patterns across the project lifecycle, using modules like git-workflow, code-review, testing-strategies, documentation-guidelines, and deployment-procedures.
How This Skill Works
As a hub, it delegates to five modules: git-workflow, code-review, testing-strategies, documentation-guidelines, and deployment-procedures. Each module defines concrete practices (repo setup, PR guidelines, test patterns, docs standards, and CI/CD pipelines) and the hub orchestrates their sequence (git-workflow first, then review, testing, documentation, deployment). Tools such as setup-validator, workflow-checker, and quality-metrics help enforce compliance.
When to Use It
- Starting a new project and wanting a fast, structured setup with git-workflow
- Scaling a team by standardizing code-review and testing
- Implementing CI/CD and reliable deployment with deployment-procedures
- Reducing documentation debt by applying documentation-guidelines
- Seeking a cohesive, modular workflow that can be extended over time
Quick Start
- Step 1: Initialize repo with git-workflow for structure and branching
- Step 2: Add code-review and testing-strategies, then documentation-guidelines
- Step 3: Enable deployment-procedures for CI/CD and monitoring
Best Practices
- Start with git-workflow to establish repository structure and branching
- Enforce a PR-based code-review process with clear guidelines
- Align unit, integration, and E2E testing via testing-strategies
- Document early with documentation-guidelines to prevent debt
- Automate CI/CD and production monitoring using deployment-procedures
Example Use Cases
- Bootstrapping a SaaS project by initializing git-workflow and code-review
- Expanding team size and adding testing-strategies for QA
- Adding documentation-guidelines to improve API docs and READMEs
- Implementing deployment-procedures for automated CI/CD and monitoring
- Using the hub to adapt the workflow as the project evolves
Frequently Asked Questions
Related Skills
webapp-testing
anthropics/skills
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
code-quality-principles
athola/claude-night-market
Provides KISS, YAGNI, and SOLID code quality principles for clean code,
hook-factory
alirezarezvani/claude-code-skill-factory
Generate production-ready Claude Code hooks with interactive Q&A, automated installation, and enhanced validation. Supports 10 templates across 7 event types for comprehensive workflow automation.
session-management
athola/claude-night-market
Manage Claude Code sessions with naming, checkpointing, and resume strategies.
multi-review
Pamacea/smite
MANDATORY gate BEFORE merging PR or deploying to production in smite project. Invoke FIRST when 'comprehensive review', 'check security', 'performance review', 'test coverage review', 'code quality audit' - orchestrates parallel review by 4 specialized agents (security, performance, testing, documentation) with consolidated report and scoring. Specific phrases: 'review this PR', 'security audit', 'performance check', 'test review'. (user)
progressive-build
Pamacea/smite
Invoke BEFORE building complex features requiring both speed AND quality in smite project - progressive enhancement workflow using Haiku (MVP in 2min) → Sonnet (quality in 5min) → Opus (excellence in 10min). Triggers on 'complex feature', 'optimize and build', 'production-ready feature', 'build with optimization'. Total: 17min, 9.5/10 quality, 73% cost savings vs Opus-only. Specific phrases: 'progressive build', 'enhance this', 'iterate and improve'. (user)