.gitmessage.txt

# <type>(<scope>): <short summary>
#
# Types:
#   feat     - new lab or project
#   fix      - bug fix or behavior correction
#   refactor - code restructuring without behavior change
#   docs     - README or documentation updates
#   style    - formatting, CSS, or non-functional UI changes
#   chore    - tooling, configuration, or maintenance tasks
#
# Scope defines WHAT area of the repo is affected.
# Use the most specific scope available.
#
# --------------------------------------------------
# Meta scopes (repo-wide changes):
#
#   repo-root     → root README.md or overall repo structure
#   standards     → CONTRIBUTING.md, commit templates, documentation standards
#   tooling       → ESLint, Prettier, package.json, config files, scripts
#
# --------------------------------------------------
# Topic folder scopes (concept-level labs):
#
#   algorithms
#   arrays
#   dom-and-events
#   logic-and-control-flow
#   loops
#   math-basics
#   mini-projects
#   objects
#   string-manipulation
#
# Use these scopes when modifying multiple labs in a topic or making
# topic-level structural changes.
#
# --------------------------------------------------
# Project scopes (use for individual lab folders with their own README):
#
#   dom-and-events/aria-tabs
#   dom-and-events/character-counter
#   dom-and-events/emoji-reactor
#   dom-and-events/favorite-icon-toggler
#   dom-and-events/football-team-cards
#   dom-and-events/instrument-filter
#   dom-and-events/lightbox-viewer
#   dom-and-events/note-taking-app
#   dom-and-events/rpsls-game
#   dom-and-events/storytelling-app
#   dom-and-events/theme-switcher
#
#   mini-projects/gradebook-app
#   mini-projects/inventory-manager
#   mini-projects/record-collection
#   mini-projects/trivia-random-answer
#
# Use project scopes when modifying a single lab or project.
#
# --------------------------------------------------
# Summary guidelines:
#
# - Use present tense ("add", not "added")
# - Be concise but descriptive
# - Do not end with a period
#
# Examples:
#
#   feat(dom-and-events/aria-tabs): add accessible tab interface lab
#
#   docs(repo-root): polish README and clarify repository structure
#
#   fix(dom-and-events/theme-switcher): restore keyboard focus after selection
#
#   chore(tooling): add ESLint and Prettier configuration
#
# --------------------------------------------------
#
# Body guidelines:
#
# - Explain WHY the change exists
# - Describe learning objective or architectural intent
# - Wrap lines at ~72 characters
# - Focus on intent, not implementation details
#
# Example body:
#
# Implements accessible tab interface using ARIA roles and synchronized
# DOM state to maintain accessibility compliance.
#
# Demonstrates proper use of aria-selected, aria-controls, tabindex,
# and hidden attributes while following repository DOM interaction
# standards.
#
# --------------------------------------------------
#
# Please enter the commit message for your changes.
# Lines starting with '#' will be ignored.
# An empty message aborts the commit.
#