name	fix-suggester
description	Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
license	MIT
metadata	{"mode":"planning","purpose":"fix"}

Fix Suggester

When to Use

A test or runtime error is reported and you need a safe, auditable fix plan.

Rules

Prefer the smallest atomic change that fixes the problem.
Include: rationale, exact patch plan (files + hunks), verification commands, and a one-line rollback.
Highlight security/auth or data-migration risks explicitly.

Output

Diagnosis: concise bullets (root cause + confidence).
Fix plan: files + short hunk descriptions.
Verify: specific commands and expected outputs.
Rollback: single command/step.

Examples

"Failing test X shows nil pointer in Y" - propose fix, tests to run, rollback.
"Login returns 500 instead of 401" - trace handler logic, propose fix.

Related Skills

safe-edit-simulator, patch-applier, test-runner

Más de este repositorio

mismo repositorio

ci-orchestrator

pilinux/gorest

Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.

2026-06-24502

linter-runner

pilinux/gorest

Execute repository linters and surface highest-priority issues with minimal, targeted fixes.

2026-06-24502

ast-introspection

pilinux/gorest

Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).

2026-02-19502

build-run

pilinux/gorest

Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.

2026-02-19502

code-formatter

pilinux/gorest

Apply repository-standard formatting to minimize diff noise and meet linter expectations.

2026-02-19502

code-navigation

pilinux/gorest

Rapid, focused navigation to locate definitions/usages and map the impact of proposed changes.

2026-02-19502

name	fix-suggester
description	Diagnose failures and propose minimal, test-backed fixes with verification and rollback instructions.
license	MIT
metadata	{"mode":"planning","purpose":"fix"}

Fix Suggester

When to Use

A test or runtime error is reported and you need a safe, auditable fix plan.

Rules

Prefer the smallest atomic change that fixes the problem.
Include: rationale, exact patch plan (files + hunks), verification commands, and a one-line rollback.
Highlight security/auth or data-migration risks explicitly.

Output

Diagnosis: concise bullets (root cause + confidence).
Fix plan: files + short hunk descriptions.
Verify: specific commands and expected outputs.
Rollback: single command/step.

Examples

"Failing test X shows nil pointer in Y" - propose fix, tests to run, rollback.
"Login returns 500 instead of 401" - trace handler logic, propose fix.

Related Skills

safe-edit-simulator, patch-applier, test-runner