菜单
Analyzes changed files and creates a git commit adhering to the Conventional Commits 1.0.0 specification. Use when asked to "commit these changes", "make a commit", "run git commit", or "save changes". Enforces branch checks, secret scanning, and mandatory Jira ticket references in the footer.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Idiomatic Go best practices for writing clean, performant, and maintainable Go code. Apply when writing, reviewing, or refactoring any Go code — including modules, packages, error handling, concurrency, CLI tools, file I/O, security, and tooling.
Creates a pull request for an infrastructure repository following the project's branch strategy, PR template, and CI requirements. Use when asked to "create a PR", "submit a pull request", "open a PR", "raise a PR for this change", or "push and create a PR". Supports Terramate, Helm, Terraform, and ArgoCD workflows.
Terraform and Infrastructure as Code optimization guidelines from Terramate. This skill should be used when writing, reviewing, or refactoring Terraform/OpenTofu code to ensure optimal patterns for security, maintainability, and reliability. Triggers on tasks involving Terraform modules, infrastructure provisioning, state management, or IaC optimization.
Terramate CLI, Cloud, and Catalyst best practices and usage guides. This skill should be used when working with Terramate stacks, orchestration, code generation, Cloud integration, or Catalyst components and bundles.
Analyzes infrastructure repository structure and recommends improvements based on best practices for Terraform modules, stack separation, Helm chart monorepos, and ArgoCD app-of-apps patterns. Use when asked to "review repo structure", "audit this repo", "suggest improvements", "refactor this repo", "restructure the repo", "assess repo layout", or "how should I organize this repo". Produces actionable findings with severity and concrete remediation steps.
Guides agents through the process of creating a new AI coding agent skill following the agentskills.io standard. Use when asked to "create a new skill", "build a skill", "write a skill", or "add a skill".
| name | commit |
| description | Analyzes changed files and creates a git commit adhering to the Conventional Commits 1.0.0 specification. Use when asked to "commit these changes", "make a commit", "run git commit", or "save changes". Enforces branch checks, secret scanning, and mandatory Jira ticket references in the footer. |
Follow these instructions to create a commit based on the project's Conventional Commits conventions.
Check the current git branch before committing:
git branch --show-current
If the current branch is main or master, stop and ask the user to create a new branch, or ask for explicit permission to commit to the main branch. Do not proceed with the commit on main or master without explicit user permission.
Review the staged and unstaged changes to understand what has been modified. Do this to structure your commit message accurately.
git status
git diff
git diff --staged
git add <files>), unless they explicitly asked you to commit everything..gitignore).Construct a commit message strictly following the Conventional Commits 1.0.0 specification.
Message Format:
<type>(scope): <description>
[optional body]
[optional footer(s)]
Refs: <Ticket-ID>
Types:
| Type | Purpose |
|---|---|
feat | New feature |
fix | Bug fix |
ref | Refactoring (no behavior change) |
perf | Performance improvement |
docs | Documentation only |
test | Test additions or corrections |
build | Build system or dependencies |
ci | CI configuration |
chore | Maintenance tasks |
style | Code formatting (no logic change) |
Subject Line Rules:
Body Guidelines:
Footer Rules:
Refs: <Ticket-ID> (e.g., Refs: JI-1234), unless explicitly instructed otherwise by the user. If the user hasn't provided a ticket ID, ask for it before proceeding.BREAKING CHANGE: <description> to the footer or include a ! immediately before the colon in the prefix (e.g., feat(api)!: <description>).Once the commit message is fully formulated and all checks pass, stop and present the final commit command to the user for review. Do not execute the commit automatically.
Provide the command in a format the user can easily copy or approve:
git commit -m "type(scope): description" -m "body text here" -m "Refs: JI-1234" -m "Co-Authored-By: <Agent Name> <Agent Email>"
Ask the user: "Does this commit message and command look correct?" Wait for their approval before proceeding to execute it upon their request.
Report back to the user that the commit has been successfully created.