skills.rest
RafayelGardishyan
RafayelGardishyanCOMMUNITY
Explore all skills by this author →
GitHub

fix

Fix lint and formatting issues in Go and frontend code.

Updated Mar 9, 2026
Search Tags:#automation#frontend#formatting#go#auto-fix#code-quality#lint
One-click install
npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill fix-rafayelgardishyan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fix
Source: https://github.com/RafayelGardishyan/rafayels-marketplace/tree/main/plugins/rafayels-engineering/.opencode/skills/fix
Command: npx skills add https://github.com/RafayelGardishyan/rafayels-marketplace --skill fix-rafayelgardishyan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps automatically fix lint and formatting issues across Go and frontend code, reducing manual edits and speeding up code quality.

Core Features & Use Cases

  • Automatic formatting for Go and frontend code, including gofmt/goimports style fixes and frontend lint/style adjustments.
  • Integration with golangci-lint and frontend tooling to identify and resolve common issues before commits.
  • Use Case: When adding new code, run the tool to automatically fix detectable violations and then run make check to confirm everything passes.

Quick Start

Run the auto-fix commands and then verify with make check.

Frequently Asked Questions about fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix lint and formatting issues in Go and frontend code?▼

To auto-fix lint and formatting issues in Go and frontend code, run the automated tool to resolve detectable violations, then verify changes by running make check to ensure everything passes before committing.

Do I need golangci-lint to auto-fix Go and frontend style violations?▼

Yes, golangci-lint is required to run and identify common issues. The tooling automatically resolves these violations alongside frontend lint checks before verifying the changes with make check.

Can I use this auto-fix approach for multi-language repositories with Go and frontend components?▼

Yes, this approach is applicable to multi-language repositories with Go and frontend components, handling formatting, imports, and style rules across modules and UI code automatically.

What is the best way to format Go and frontend code before a commit?▼

The best way to format Go and frontend code before a commit is to run auto-fix commands that handle gofmt and goimports style fixes, followed by running make check to confirm all CI checks pass.

Why does auto-fixing lint issues require running make check afterwards?▼

Running make check afterwards is required to verify that the auto-fixes applied by the lint tooling pass all CI checks, ensuring the Go and frontend code remains clean and consistent.

Related Skills

Explore More Software Engineering Skills→
yu-iskwyu-iskw
1

lint-and-fix

Format code and fix lint violations with trunk-based tooling.

Community
Intermediate
daodaoedudaodaoedu

pre-commit-check

Run make check and make lint, then auto-fix with make format.

Official
Intermediate
carayacaraya
1

go-formatting

Automate Go code formatting with gofmt, goimports, and golangci-lint.

Community
Intermediate
Mekann2904Mekann2904

lint-analyzer

Analyzes code quality across JavaScript, Python, Ruby, and Go using standard linting tools.

Community
Intermediate