Template

Files

lmiranda e5ca804692 feat: v3.0.0 architecture overhaul

- Rename marketplace to lm-claude-plugins
- Move MCP servers to root with symlinks
- Add 6 PR tools to Gitea MCP (list_pull_requests, get_pull_request,
  get_pr_diff, get_pr_comments, create_pr_review, add_pr_comment)
- Add clarity-assist plugin (prompt optimization with ND accommodations)
- Add git-flow plugin (workflow automation)
- Add pr-review plugin (multi-agent review with confidence scoring)
- Centralize configuration docs
- Update all documentation for v3.0.0

BREAKING CHANGE: MCP server paths changed, marketplace renamed

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-20 16:56:53 -05:00

2.4 KiB

Raw Blame History

/commit - Smart Commit

Purpose

Create a git commit with an auto-generated conventional commit message based on staged changes.

Behavior

Step 1: Analyze Changes

Run git status to see staged and unstaged changes
Run git diff --staged to examine staged changes
If nothing staged, prompt user to stage changes

Step 2: Generate Commit Message

Analyze the changes and generate a conventional commit message:

<type>(<scope>): <description>

[optional body]

[optional footer]

Types:

feat: New feature
fix: Bug fix
docs: Documentation only
style: Formatting, missing semicolons, etc.
refactor: Code change that neither fixes a bug nor adds a feature
perf: Performance improvement
test: Adding/updating tests
chore: Maintenance tasks
build: Build system or external dependencies
ci: CI configuration

Scope: Determined from changed files (e.g., auth, api, ui)

Step 3: Confirm or Edit

Present the generated message:

Proposed commit message:
───────────────────────
feat(auth): add password reset functionality

Implement forgot password flow with email verification.
Includes rate limiting and token expiration.
───────────────────────

Options:
1. Use this message (Recommended)
2. Edit the message
3. Regenerate with different focus
4. Cancel

Step 4: Execute Commit

If confirmed, run:

git commit -m "$(cat <<'EOF'
<message>

Co-Authored-By: Claude <noreply@anthropic.com>
EOF
)"

Environment Variables

Variable	Default	Description
`GIT_COMMIT_STYLE`	`conventional`	Message style (conventional, simple, detailed)
`GIT_SIGN_COMMITS`	`false`	Use GPG signing
`GIT_CO_AUTHOR`	`true`	Include Claude co-author footer

Edge Cases

No Changes Staged

No changes staged for commit.

Would you like to:
1. Stage all changes (`git add -A`)
2. Stage specific files (I'll help you choose)
3. Cancel

Untracked Files

Found 3 untracked files:
- src/new-feature.ts
- tests/new-feature.test.ts
- docs/new-feature.md

Include these in the commit?
1. Yes, stage all (Recommended)
2. Let me pick which ones
3. No, commit only tracked files

Output

On success:

Committed: abc1234
feat(auth): add password reset functionality

Files: 3 changed, 45 insertions(+), 12 deletions(-)

2.4 KiB Raw Blame History