Some checks failed
Deploy analytics worker / Deploy analytics worker to ${{ (github.ref == 'refs/heads/production' && 'production') || (github.ref == 'refs/heads/main' && 'staging') || 'preview' }} (push) Failing after 1s
i18n upload strings / Upload latest strings (push) Failing after 1s
Deploy bemo / Deploy bemo to ${{ (github.ref == 'refs/heads/bemo-production' && 'production') || (github.ref == 'refs/heads/main' && 'staging') || 'preview' }} (push) Failing after 1s
Deploy grafana resources / ${{ github.event_name == 'push' && 'Deploy grafana resources' || 'Validate grafana resources (dry run)' }} (push) Failing after 0s
End to end tests (dotcom) / Check for relevant changes (push) Failing after 0s
End to end tests (examples) / Check for relevant changes (push) Failing after 0s
End to end tests (mermaid readability) / Check for relevant changes (push) Failing after 1s
End to end tests (perf) / Check for relevant changes (push) Failing after 0s
Publish editor extensions / Publish editor extensions (push) Failing after 1s
Publish SDK packages / Remove the publish-packages label (push) Has been skipped
Checks / Tests & checks (push) Has been cancelled
Checks / Build all projects (push) Has been cancelled
Deploy templates / Deploy templates (push) Has been cancelled
End to end tests (dotcom) / End to end tests (dotcom) (push) Has been cancelled
End to end tests (mermaid readability) / End to end tests (mermaid readability) (push) Has been cancelled
End to end tests (perf) / End to end tests (perf) (push) Has been cancelled
Deploy .com / Deploy dotcom to ${{ (github.ref == 'refs/heads/production' && 'production') || (github.ref == 'refs/heads/main' && 'staging') || 'preview' }} (push) Has been cancelled
End to end tests (examples) / End to end tests (examples) (push) Has been cancelled
Publish SDK packages / Publish SDK packages (push) Has been cancelled
Publish SDK packages / Tell user released version (push) Has been cancelled
Publish SDK packages / Publishes code templates to separate repositories (push) Has been cancelled
Publish SDK packages / Deploys the template demos with the new SDK version (push) Has been cancelled
49 lines
1.7 KiB
Markdown
49 lines
1.7 KiB
Markdown
---
|
|
name: commit-changes
|
|
description: Create a git commit for the current changes. Use when asked to commit changes, make a commit, generate a commit message, or commit the current worktree with optional user-provided context.
|
|
---
|
|
|
|
# Commit changes
|
|
|
|
Create a focused git commit for the current changes.
|
|
|
|
## Workflow
|
|
|
|
1. Gather context:
|
|
- User notes, if provided.
|
|
- Current branch: `git branch --show-current`.
|
|
- Working tree: `git status --short`.
|
|
- Staged changes: `git diff --cached --stat`.
|
|
- Unstaged changes: `git diff --stat`.
|
|
- Recent commits for style reference: `git log -5 --oneline`.
|
|
2. Review the changed files.
|
|
3. If there are no changes to commit, tell the user and stop.
|
|
4. If there are unstaged changes, stage the relevant files with `git add`.
|
|
5. Do not stage files that look like secrets, credentials, API keys, or private environment files.
|
|
6. Write a conventional commit message:
|
|
|
|
```text
|
|
type(scope): brief description
|
|
|
|
Optional longer explanation if the changes are complex.
|
|
```
|
|
|
|
Allowed types: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`, `perf`, `style`, `build`, `ci`.
|
|
|
|
## Message guidelines
|
|
|
|
- Keep the first line under 72 characters.
|
|
- Use imperative mood, for example `add feature`, not `added feature`.
|
|
- Be specific about what changed and why.
|
|
- Incorporate user-provided context when it clarifies intent.
|
|
|
|
## Commit rules
|
|
|
|
- Use `git commit -m "message"`.
|
|
- Do not push.
|
|
- Do not amend unless explicitly requested.
|
|
- Do not use `--no-verify`.
|
|
- Do not include AI attribution.
|
|
|
|
If the commit fails because of hooks, fix mechanical formatting, lint, or import issues and retry. If the hook failure reveals a meaningful product or implementation issue, stop and ask the user how to proceed.
|