This document outlines the contribution process for DUCA’s projects.

📝 Development Workflow

🌱 Branch Naming Convention

feature/command-name         # New features
fix/issue-description        # Bug fixes
docs/section-name            # Documentation updates
refactor/component-name      # Code refactoring
hotfix/critical-issue        # Critical production fixes

✒️ Commit Message Format

We follow the Conventional Commits specification:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types:

• feat: New feature
• fix: Bug fix
• docs: Documentation changes
• style: Formatting, missing semicolons, etc.
• refactor: Code change that neither fixes a bug nor adds a feature
• test: Adding missing tests
• chore: Changes to build process or auxiliary tools

Examples:

feat(commands): add weather command with location support
fix(verify): resolve email validation bug for .edu domains
docs(readme): update installation instructions
refactor(utils): optimize database connection handling

🙌 Thank You!

We appreciate your time and effort ❤️