Run the following steps to stage and commit all changes in the current git repository with a professional commit message.

Run git status to identify all modified, added, and deleted files.
Run git diff and git diff --cached to understand exactly what changed.
Run git log --oneline -5 to match the existing commit message style of this repo.
Run git add on all relevant changed files. Avoid staging these files — warn the user if they are present:
- .env files
- settings.local.json
- Any file in 02-Eve-ng-Setup/eveng-mcp/
- Large binary files
Craft a commit message following these rules:
- Subject line: imperative mood, max 72 characters, no trailing period
- Examples: "Add RSTP notes and verification commands to module 26", "Add STP PortFast lab guide for module 24"
- Body (optional): one blank line after subject, explain why not just what, wrap at 72 chars
- Be specific to the actual changes — never use generic messages like "update files" or "minor changes"
- If multiple unrelated changes exist, group them logically in the body
Commit using a HEREDOC to preserve formatting.
Run git status after the commit to confirm a clean working tree.
Show the user the commit hash and subject line.

Do not push to remote. Do not amend existing commits. If there is nothing to commit, say so clearly.

Run git status to identify all modified, added, and deleted files.
Run git diff and git diff --cached to understand exactly what changed.
Run git log --oneline -5 to match the existing commit message style of this repo.
Run git add on all relevant changed files. Avoid staging these files — warn the user if they are present:
- .env files
- settings.local.json
- Any file in 02-Eve-ng-Setup/eveng-mcp/
- Large binary files
Craft a commit message following these rules:
- Subject line: imperative mood, max 72 characters, no trailing period
- Examples: "Add RSTP notes and verification commands to module 26", "Add STP PortFast lab guide for module 24"
- Body (optional): one blank line after subject, explain why not just what, wrap at 72 chars
- Be specific to the actual changes — never use generic messages like "update files" or "minor changes"
- If multiple unrelated changes exist, group them logically in the body
Commit using a HEREDOC to preserve formatting.
Run git status after the commit to confirm a clean working tree.
Show the user the commit hash and subject line.

Do not push to remote. Do not amend existing commits. If there is nothing to commit, say so clearly.

Related Skills