Files
leo-claude-mktplace/plugins/git-flow/commands/git-status.md
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

1.9 KiB

/git-status - Enhanced Status

Purpose

Show comprehensive git status with recommendations and insights.

Behavior

Output Format

═══════════════════════════════════════════
Git Status: <repo-name>
═══════════════════════════════════════════

Branch: feat/password-reset
Base: development (3 commits ahead, 0 behind)
Remote: origin/feat/password-reset (synced)

─── Changes ───────────────────────────────

Staged (ready to commit):
  ✓ src/auth/reset.ts (modified)
  ✓ src/auth/types.ts (modified)

Unstaged:
  • tests/auth.test.ts (modified)
  • src/utils/email.ts (new file, untracked)

─── Recommendations ───────────────────────

1. Stage test file: git add tests/auth.test.ts
2. Consider adding new file: git add src/utils/email.ts
3. Ready to commit with 2 staged files

─── Quick Actions ─────────────────────────

• /commit - Commit staged changes
• /commit-push - Commit and push
• /commit-sync - Full sync with development

═══════════════════════════════════════════

Analysis Provided

Branch Health

  • Commits ahead/behind base branch
  • Sync status with remote
  • Age of branch

Change Categories

  • Staged (ready to commit)
  • Modified (not staged)
  • Untracked (new files)
  • Deleted
  • Renamed

Recommendations

  • What to stage
  • What to ignore
  • When to commit
  • When to sync

Warnings

  • Large number of changes (consider splitting)
  • Old branch (consider rebasing)
  • Conflicts with upstream

Output

Always produces the formatted status report with context-aware recommendations.