based on this article

Conventional Commits

Basic Format

Standard commit message structure:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Important Labels

• feat : New feature for the user
• fix : Bug fix
• docs : Documentation only changes
• style : Formatting, missing semicolons (no code change)
• refactor : Code refactoring (neither new feature nor bug fix)
• test : Adding or modifying tests
• chore : Maintenance tasks, build processes, etc.
• merge : Merge operation

Minishell Examples

Scope (optional)

feat(parser): ...     # Scope = parser
fix(builtin): ...     # Scope = builtin
docs: ...            # No scope

feat(parser): add command tokenization
fix(builtin): correct cd behavior with relative paths
docs(readme): add installation instructions
style(parser): fix indentation and formatting
refactor(executor): extract pipe handling to separate function
test(builtins): add unit tests for echo command
perf(lexer): optimize token parsing algorithm

Use feat and fix primarily, add logical scope, keep description clear and concise.