code-formatting
Enforces mandatory Go testing naming conventions and linting workflows through specific command execution.
Install
mkdir -p .claude/skills/code-formatting && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/3586" && unzip -o skill.zip -d .claude/skills/code-formatting && rm skill.zipInstalls to .claude/skills/code-formatting
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
MANDATORY: When writing Go tests, you MUST use 'When...it should...' format for ALL test names. When writing any Go code, you MUST remind user to run 'make lint-fix' and 'make verify'. These are non-negotiable HyperShift requirements.Key capabilities
- →Enforce Go test naming conventions
- →Automate linting fixes
- →Verify code quality with make commands
- →Standardize unit test placement
- →Validate markdown spelling
How it works
The skill enforces mandatory naming formats for Go tests and requires the execution of specific make commands to ensure code quality and verification.
Inputs & outputs
When to use code-formatting
- →Validating Go test naming conventions
- →Running linting fixes before commits
- →Standardizing Go project verification
About code-formatting
Ensures adherence to mandatory Go testing formats and linting workflows. Requires 'When...it should...' test naming and specific command execution for verification.
MANDATORY: When writing Go tests, you MUST use 'When...it should...' format for ALL test names. When writing any Go code, you MUST remind user to run 'make lint-fix' and 'make verify'. These are non-negotiable HyperShift requirements.
When not to use it
- →When the project is not a Go-based HyperShift repository
- →When the user refuses to follow naming conventions
Prerequisites
Limitations
- →Naming conventions are non-negotiable
- →Requires specific make targets to be present
How it compares
It mandates strict, non-negotiable naming conventions and verification workflows specific to HyperShift requirements.
Compared to similar skills
code-formatting side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| code-formatting (this skill) | 1 | 2mo | No flags | Beginner |
| go-dev-guidelines | 14 | 9mo | No flags | Intermediate |
| tidb-test-guidelines | 2 | 28d | No flags | Intermediate |
| lsp-hover-testing | 1 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by openshift
View all by openshift →You might also like
go-dev-guidelines
jumppad-labs
This skill should be used when writing, refactoring, or testing Go code. It provides idiomatic Go development patterns, TDD-based workflows, project structure conventions, and testing best practices using testify/require and mockery. Activate this skill when creating new Go features, services, packages, tests, or when setting up new Go projects.
tidb-test-guidelines
pingcap
Decide where to place TiDB tests and how to write them (basic structure, naming, testdata usage). Use when asked about test locations, writing conventions, shard_count limits, casetest categorization, or when reviewing test changes in code review.
lsp-hover-testing
MadAppGang
Automated LSP hover validation for Dingo transpiler. Use when testing hover functionality, validating position mappings, checking for hover drift, or debugging LSP issues after sourcemap changes.
go-rig
mudrii
Use this skill when building, reviewing, or refactoring Go code in this repository. It adds process discipline for TDD/ATDD, package boundaries, dependency injection, and review quality, and complements the always-on rules in AGENTS.md.
code-coverage
viknesh20-20
Analyzes test coverage, identifies untested code paths, and generates tests for the most critical uncovered areas. Use to improve test coverage before releases.
go-review-pr
JotJunior
Review all changes in the current branch against GOB project conventions before opening a PR. Diff-aware: only analyzes what changed, not the entire codebase. Triggers: \"review pr\", \"revisar pr\", \"pre-pr check\", \"review branch\", \"revisar branch\", \"checar antes do pr\", \"quality gate\".