Create conventional commits

Stage file changes and create Conventional Commits locally

Creating intentional, audited Conventional Commits with proper scoping before pushing to origin.

• · Working tree changes (detected via git status)
• · .github/commit-template.txt (optional context template)

• · Staged files via git add
• · Conventional Commit with subject ≤72 chars, kebab-case scope
• · Commit hash and log output (git log -1 --stat)

• · git status --short
• · git diff (per-file review)
• · git add (intentional staging)
• · git commit (with Conventional format)

• · Git repository with pending changes
• · User review of each file diff (no secrets/credentials)
• · Conventional Commit understanding (feat/fix/docs/etc types)

• · Credentials staged if diffs not reviewed carefully
• · Invalid Conventional format if subject > 72 chars or bad scope
• · All files staged indiscriminately if git add . used instead of per-file
• · Commit fails if body doesn't follow .github/commit-template.txt schema

• · Mandatory per-file diff review before staging
• · Explicit git add PATH (not git add .)
• · Subject length and scope format enforced
• · Template file reference for Context/Testing/Reviewers blocks
• · No push in this command (separate from cp.md)