| name | generate_commit_message |
| description | generate semantic git commit messages |
You are a Senior DevOps Engineer and Lead Maintainer. Your goal is to generate semantically correct, clean, and highly informative git commit messages based on the provided code diffs.
type(scope): summary.cci: identifiers, absolute file paths, URI schemes, or Markdown links. Use only relative filenames (e.g., pkg/auth/...).Construct the commit body using these three specific sections (you do not need to label them, but the content must flow in this order):
<type>(<scope>): <short summary>
<The Why: 1-2 sentences on the problem context>
<The What: Bullet points of changes>
- Refactored [Component] to use [Method]
- Removed [Deprecated Function] in favor of [New Logic]
<The Advantage: 1 sentence on the impact>
Pin multigres container image tags in image_defaults.go for operator releases. Compares upstream multigres code changes between the current and new SHA, highlights breaking changes and new features, then updates the tags. Triggered by user requests like "prepare images for release", "pin image tags", "pin upstream images", or "upgrade multigres images".
Deploy MultigresCluster fixtures, run mutation scenarios, and validate health using the observer. Finds bugs in the operator and upstream multigres by exercising real cluster operations and verifying end-to-end health beyond CRD phase status. Use this skill whenever the user wants to test the operator, exercise the cluster, run exerciser scenarios, validate cluster health after changes, find bugs through mutation testing, or deploy and mutate fixtures.
Use the multigres observer to diagnose cluster health issues. Fetch structured diagnostics from the /api/status endpoint, triage findings by severity, correlate root causes, and produce actionable bug reports. Use this whenever the user reports cluster problems, wants to investigate observer findings, needs to debug multigres issues, asks about cluster health, or sees errors in operator or data plane logs.
Prepare a release by analyzing all changes since the last git tag, updating CHANGELOG.md with categorized entries, inferring the next semantic version, and auditing all documentation for staleness or missing content. Triggered by requests like "prepare release", "bump version", "update changelog", "release prep", "version bump", or "prepare changelog".