name	patch-applier
description	Draft and apply small, atomic patches; always present a preview diff and appropriate verification commands.
license	MIT
metadata	{"mode":"edit","purpose":"patch"}

Patch Applier

When to Use

You have a focused code change that should be applied and reviewed as a single patch.

Rules

Keep patches atomic and single-purpose.
Show a preview (paths + short hunk summary) before applying.
After applying, run formatting, linters, and targeted tests as appropriate.

Workflow

Locate edit points via source-search or file-reader.
Draft patch and show a preview for approval.
Apply patch and run go fmt ./... / golangci-lint run ./... / targeted go test.
Report modified files and verification results.

Output

Patch summary: 1-3 bullets.
Files changed: list with path:line.
Verification: commands and results.

Related Skills

safe-edit-simulator, code-formatter, 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	patch-applier
description	Draft and apply small, atomic patches; always present a preview diff and appropriate verification commands.
license	MIT
metadata	{"mode":"edit","purpose":"patch"}

Patch Applier

When to Use

You have a focused code change that should be applied and reviewed as a single patch.

Rules

Keep patches atomic and single-purpose.
Show a preview (paths + short hunk summary) before applying.
After applying, run formatting, linters, and targeted tests as appropriate.

Workflow

Locate edit points via source-search or file-reader.
Draft patch and show a preview for approval.
Apply patch and run go fmt ./... / golangci-lint run ./... / targeted go test.
Report modified files and verification results.

Output

Patch summary: 1-3 bullets.
Files changed: list with path:line.
Verification: commands and results.

Related Skills

safe-edit-simulator, code-formatter, test-runner