execute-coding-guideline-fix

Refactors code against coding guidelines in bounded 5-8 file micro-batches.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill execute-coding-guideline-fix-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-coding-guideline-fix
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/execute-coding-guideline-fix
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill execute-coding-guideline-fix-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Enforcing coding guidelines across a large codebase manually is slow and inconsistent. This Skill autonomously fixes violations such as explicit boolean comparisons, deep nesting, poor naming, and oversized functions in strictly bounded micro-batches of 5-8 files. ## Core Features & Use Cases - Guideline Enforcement: Applies rules for implicit booleans, affirmative naming (isDefined, isValid), guard clauses, and mandatory blank-line spacing. - Go Error Handling Modernization: Replaces multi-value error tuples with appfault.Result[T] containers and pointer-safe receiver methods. - Atomic Workflow Discipline: Tracks modified files in a change inventory, runs targeted linters per batch, and produces a single consolidated commit pushed to remote. - Use Case: A team maintaining a Go monorepo needs to migrate legacy code to new naming and error-handling standards without breaking CI; the Skill processes files in small verified batches and commits atomically. ## Quick Start Ask the agent to run the coding guideline fix on the next batch of Go files in the target package and commit the results.

Frequently Asked Questions about execute-coding-guideline-fix

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

FAQPage Schema
How do I automatically fix coding guideline violations in a Go codebase?

Run the guideline fix workflow, which scans target files, applies rules for implicit booleans, affirmative naming, guard clauses, and Result-based error handling, then verifies each 5-8 file batch with targeted linters before committing.

How to refactor boolean naming like isNotValid or hasNoValue?

Replace negative identifiers with affirmative forms such as isValid or hasValue, and invert at the call site with a negation operator when testing for absence. Single-letter and bare boolean names are renamed to forms like isStopped or isDefined.

Does this workflow run tests or builds during refactoring?

No. Test execution and build checks are strictly banned during routine turns. Only targeted linters run on modified batch files, while full testing and builds are deferred to CI/CD pipelines.

Why are changes committed in one atomic commit instead of per file?

Per-file commits pollute git history, create subagent lock collisions, and break atomic rollback. All modified files, plans, and change records are accumulated and committed together in a single conventional commit, then pushed immediately.

What are the limitations of batch-based guideline refactoring?

Each turn processes only 5-8 files, so large codebases require multiple turns. It also cannot verify compilation locally, meaning type errors surface only in CI/CD after the push.