agd:commit | agentic-doc | ClaudePluginHub

Generate a Conventional Commits message from staged changes and create the commit.

Core Principle

Human owns the commit. Never add Co-Authored-By footer for AI assistance. The human takes full responsibility for all commits in their repository.

Load Context

First, load the conventional-commits skill to understand commit format and best practices:

Use Skill tool with skill="agd:conventional-commits"

This provides:

Conventional Commits types and usage
Style rules (imperative mood, no capitalization, etc.)
Examples of good and bad commit messages
Co-Authored-By guidance (never for AI)

Process

Check git status:
```
git status --short
```
Identify unstaged files (lines where first column is space, ?, or has changes not yet staged).

Handle staging decision:

Call the AskUserQuestion tool with these parameters:

{
  "questions": [{
    "question": "There are unstaged changes. Would you like me to stage them?",
    "header": "Stage changes",
    "options": [
      {"label": "Stage all", "description": "Run 'git add -A' to stage all changes"},
      {"label": "Skip staging", "description": "Commit only currently staged changes"}
    ]
  }]
}

Wait for the tool response, then:

"Stage all" → Run git add -A, then continue to step 3
"Skip staging" → Continue to step 3 with current staged changes

If no unstaged changes exist, skip this step and continue directly to step 3.

Analyze the diff to determine:
- Type: Use types from the loaded skill (feat, fix, docs, etc.)
- Scope: If provided via argument, use it. Otherwise infer from changed files.
- Description: Follow style rules from the skill
- Body: Check change size/complexity per skill's "When to Add Body" section
Generate commit message:
- For small/simple changes: <type>[scope]: <description>
- For large/complex changes: Include body with what/why/impact
Important: Do NOT add Co-Authored-By footer. The commit belongs to the human user.

Get human confirmation:

Call the AskUserQuestion tool to get approval:

{
  "questions": [{
    "question": "Ready to commit with this message:\n\n<commit message>\n\nProceed?",
    "header": "Confirm commit",
    "options": [
      {"label": "Yes, commit", "description": "Create the commit with this message"},
      {"label": "Edit message", "description": "Provide a custom commit message instead"}
    ]
  }]
}

If "Yes, commit" → Proceed to step 6
If "Edit message" → Ask user for custom message, then proceed to step 6

Create the commit:
- For single-line: git commit -m "<type>[scope]: <description>"
- For multi-line: git commit -m "<type>[scope]: <description>" -m "<body line 1>" -m "<body line 2>"

Error Handling

When unstaged changes exist, ask user via AskUserQuestion before proceeding to step 3
If no changes at all (staged or unstaged), inform user and exit
Follow breaking change format from the skill when applicable
Always get human confirmation before executing git commit

Load Context

First, load the conventional-commits skill to understand commit format and best practices:

Use Skill tool with skill="agd:conventional-commits"

This provides:

Conventional Commits types and usage

Style rules (imperative mood, no capitalization, etc.)

Examples of good and bad commit messages

Co-Authored-By guidance (never for AI)

Process

Check git status:

git status --short

Identify unstaged files (lines where first column is space, ?, or has changes not yet staged).

Handle staging decision:

Call the AskUserQuestion tool with these parameters:

{
  "questions": [{
    "question": "There are unstaged changes. Would you like me to stage them?",
    "header": "Stage changes",
    "options": [
      {"label": "Stage all", "description": "Run 'git add -A' to stage all changes"},
      {"label": "Skip staging", "description": "Commit only currently staged changes"}
    ]
  }]
}

Wait for the tool response, then:

"Stage all" → Run git add -A, then continue to step 3
"Skip staging" → Continue to step 3 with current staged changes

If no unstaged changes exist, skip this step and continue directly to step 3.

Analyze the diff to determine:

Type: Use types from the loaded skill (feat, fix, docs, etc.)
Scope: If provided via argument, use it. Otherwise infer from changed files.
Description: Follow style rules from the skill
Body: Check change size/complexity per skill's "When to Add Body" section

Generate commit message:

For small/simple changes: <type>[scope]: <description>
For large/complex changes: Include body with what/why/impact

Important: Do NOT add Co-Authored-By footer. The commit belongs to the human user.

Get human confirmation:

Call the AskUserQuestion tool to get approval:

{
  "questions": [{
    "question": "Ready to commit with this message:\n\n<commit message>\n\nProceed?",
    "header": "Confirm commit",
    "options": [
      {"label": "Yes, commit", "description": "Create the commit with this message"},
      {"label": "Edit message", "description": "Provide a custom commit message instead"}
    ]
  }]
}

If "Yes, commit" → Proceed to step 6
If "Edit message" → Ask user for custom message, then proceed to step 6

Create the commit:

For single-line: git commit -m "<type>[scope]: <description>"
For multi-line: git commit -m "<type>[scope]: <description>" -m "<body line 1>" -m "<body line 2>"