doc: create documentation for Conventional Commits

[p-iknow]

Requirement

Resolves #9

Create comprehensive documentation for Conventional Commits that serves as the source of truth for our commit conventions, with clear guidelines on what commit formats we use, why we chose these formats, example use cases, and how they map to issue templates.

Implementation

Documentation Files Created

• docs/CONVENTIONAL_COMMITS.md - Complete English documentation (489 lines)

  • Overview section explaining why we use Conventional Commits and link to official spec
  • Detailed documentation of all 9 commit types: feat, fix, doc, config, refactor, agent, format, test, perf
  • Each type includes: definition, when to use, examples, and anti-patterns
  • Scope usage guidelines with syntax and examples
  • Commit type to issue template mapping table
  • Real-world scenario matrix for quick reference
  • "Requirement" vs "Goal" usage guidelines
  • Current limitations section documenting gaps (format type has no issue template, bug vs fix terminology)
  • Links to custom commands that enforce conventions (/make-commit, /make-branch, /make-pr)

• docs/CONVENTIONAL_COMMITS.ko.md - Korean translation (489 lines)

  • Full Korean translation of the documentation
  • Technical terms and code examples preserved in English
  • Explanations and guidelines translated to Korean

README Updates

• README.md - Added link to docs/CONVENTIONAL_COMMITS.md in Features section and Repository Contents
• README.ko.md - Added link to docs/CONVENTIONAL_COMMITS.ko.md in Features section and Repository Contents

Key Features

• Comprehensive coverage of all 9 commit types used in the project
• Direct mapping between commit types and issue templates
• Real-world scenarios with matching commit examples
• Current limitations clearly documented
• Bilingual support (English and Korean)

Test

• Documentation reviewed for accuracy
• All commit types match custom commands in .claude/commands/
• All commit types match issue templates in .github/ISSUE_TEMPLATE/
• Links and references properly connected
• Consistency with existing documentation maintained
• Korean translation preserves technical terms correctly

Reference

• https://www.conventionalcommits.org/ - Official Conventional Commits specification
• Custom commands: /make-commit, /make-branch, /make-pr

Human Check

🤖 Generated with Claude Code

• I reviewed it