Go Contributor

VerifiedSafe

Helps format and check Go commit messages according to project standards. Also assists with using the git-codereview tool to interact with Gerrit for code review. Useful when contributing to the Go project and following its contribution workflow.

Sby Skills Guide Bot
DevelopmentIntermediate
6/2/2026
Claude Code
#go#gerrit#git#contribution

Recommended for

Automated summary

This skill helps with contributing to the Go project by formatting and checking commit messages and interacting with Gerrit.

Strengths

  • Provides strict formatting guidelines for Go commit messages.
  • Integrates git-codereview for Gerrit workflow (change, mail, sync, submit).
  • Includes a script to validate commit messages.
  • Covers Gerrit voting rules and trybot usage.

Limitations

  • Requires git-codereview to be installed and configured.
  • Does not handle advanced merge conflict resolution.
  • The validation script is only available locally.
When to use it

Use this skill when preparing a contribution to the Go project and you need to format or check a commit message according to official standards.

When not to use it

Do not use it for projects that do not use Gerrit or for contributions that do not follow the Go workflow.

Security analysis

Safe
Quality score90/100

The skill uses git, git-codereview, and a bash script for commit message validation, all standard tools for Go contribution. No destructive or exfiltrating commands are present, and no obfuscated payloads.

No concerns found

How this analysis is made

Examples

Format a commit message for a Go change
I need to write a commit message for a change in the 'math' package that fixes an overflow issue. Help me format it properly according to Go conventions.
Check an existing commit message
Check this Go commit message for compliance: 'fix: resolve overflow in math package'
Send changes to Gerrit
I have made some changes to the Go source code. How do I use git-codereview to mail them for review?

name: go-contributor description: Helps with contributing to the Go project. Use when you need to format or check a commit message for Go standards or interact with Gerrit using the git-codereview tool. license: Apache-2.0 metadata: category: development tags: [go, gerrit, git, contribution] allowed-tools: [git, git-codereview, bash] compatibility: gemini-cli: ">=0.30.0"

Go Contributor Skill

This skill helps you follow the Go contribution process, specifically focusing on commit message formatting and interaction with Gerrit.

Workflows

1. Formatting a Commit Message

A good Go commit message follows a strict format:

  • First Line: Prefix with package (e.g., math: ). Summary should complete "This change modifies Go to _____." No leading capital, no trailing period.
  • Body: Detailed context, wrap at 72 columns, blank line after first line.
  • Issues: Use Fixes #12345 or Updates #12345. For x/ repositories, use Fixes golang/go#12345.

See references/commit_message_template.md for more details.

2. Checking a Commit Message

You can use the provided script to validate a commit message:

./scripts/check_commit_msg.sh <commit_msg_file>

3. Interacting with Gerrit

Use the git-codereview tool (often aliased to git).

  • git codereview change: Create or amend a single commit in your branch.
  • git codereview mail: Send your changes to Gerrit for review.
  • git codereview sync: Sync your local branch with the master.
  • git codereview submit: Submit an approved change (usually done by maintainers).

Additional Resources

  • Gerrit Review Voting:
    • +1: Looks good, but may need minor changes or reviewer is not an approver.
    • +2: Approved for merge (only by maintainers).
    • Hold +1: Do not submit yet.
  • Trybots: Triggered by maintainers to run full test suite. Failures must be fixed and re-uploaded.

Common Shortcuts

Add these to your .gitconfig:

[alias]
    change = codereview change
    gofmt = codereview gofmt
    mail = codereview mail
    pending = codereview pending
    submit = codereview submit
    sync = codereview sync

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/go-contributor-mm8o521r/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/go-contributor-mm8o521r' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/go-contributor-mm8o521r/download' --output '.skill-downloads/go-contributor-mm8o521r/SKILL.md.part' && mv '.skill-downloads/go-contributor-mm8o521r/SKILL.md.part' '.skill-downloads/go-contributor-mm8o521r/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/go-contributor-mm8o521r/SKILL.md' && test -s '.skill-downloads/go-contributor-mm8o521r/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/go-contributor' && cp -R '.skill-downloads/go-contributor-mm8o521r' '.claude/skills/go-contributor'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/go-contributor-mm8o521r'

openskills read 'go-contributor-mm8o521r'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/go-contributor-mm8o521r/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills