improve-backend

Identify and fix the highest-priority security, stability, performance, and simplicity issues in a Go backend.

411|21|Updated Dec 18, 2025

Search Tags:#performance #stability #concurrency #go #code audit #backend security #code simplification

Ready to run

npx skills add https://github.com/luxury-yacht/app --skill improve-backend

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: improve-backend
Source: https://github.com/luxury-yacht/app/tree/main/.agents/skills/improve-backend
Command: npx skills add https://github.com/luxury-yacht/app --skill improve-backend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you systematically improve a Go backend by finding high-impact security, stability, performance, and simplicity risks before they turn into outages, vulnerabilities, or slowdowns.

Core Features & Use Cases

Ranked backend findings: Scans for concrete issues and returns exactly 5 prioritized items so you can quickly choose what to address first.
Security-first workflow: Detects common Go/backend risk patterns such as input validation gaps, secret exposure, RBAC weaknesses, concurrency hazards, and error-handling problems.
Actionable fixes: After you select one finding, it applies a minimal correct fix, updates tests, and verifies via the project’s quality checks, while checking cross-boundary effects for frontend assumptions.

Quick Start

Run: /improve-backend refresh to focus the scan on the refresh-related backend code and then pick one of the five ranked fixes to apply.

Frequently Asked Questions about improve-backend

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

FAQPage Schema

How do I find and fix high-priority security and stability issues in a Go backend?▼

To fix Go backend security and stability issues, you can run a code audit that identifies the top five ranked risks and applies minimal refactors to the selected problem. It scans for input validation gaps, concurrency hazards, and error-handling problems, then verifies the fix using your project's quality checks.

What is the best way to audit Go backend performance without rewriting large parts of the system?▼

The best way to audit Go backend performance without major rewrites is to use a targeted code audit that produces five ranked findings. It applies minimal changes to the selected performance issue and runs quality checks to ensure stability without altering large parts of the system.

How do I prioritize backend refactors for concurrency hazards and error handling?▼

To prioritize backend refactors for concurrency hazards and error handling, you need a workflow that returns five ranked findings with severity and impact levels. You then select the highest-priority issue to apply a minimal correct fix while updating tests to prevent outages.

Can I scope a Go backend code audit to a specific area like a refresh endpoint?▼

Yes, you can scope a Go backend code audit to a specific area by passing an area argument like refresh. This focuses the scan on the targeted backend code to identify security, performance, and simplicity issues within that specific boundary before applying fixes.

Does applying a minimal fix to backend code check for cross-boundary effects on frontend assumptions?▼

Yes, applying a minimal fix to backend code checks for cross-boundary effects on frontend assumptions. After you select one of the five ranked findings, the workflow applies the fix, updates tests, and verifies cross-boundary impacts before running the project's quality checks.