coding-prompt-normalizer

Convert messy coding requests into structured task-context handoff prompts for coding agents.

1|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/GonkaGate/opencode-setup --skill coding-prompt-normalizer-gonkagate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-prompt-normalizer
Source: https://github.com/GonkaGate/opencode-setup/tree/main/.agents/skills/coding-prompt-normalizer
Command: npx skills add https://github.com/GonkaGate/opencode-setup --skill coding-prompt-normalizer-gonkagate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Rough, mixed-language, dictated, or repetitive coding requests often lose critical technical details when passed to a coding agent, causing the agent to misunderstand the task or start in the wrong place. This Skill reconstructs the user's real intent, preserves exact technical literals, and packages the result as a repo-aware handoff prompt. ## Core Features & Use Cases - Intent Reconstruction: Cleans filler, duplicates, and false starts from noisy input while preserving exact file paths, CLI commands, config keys, and code identifiers verbatim. - Task Mode Classification: Routes each request to the right mode (implementation, bug-investigation, review-read-only, refactor, planning-spec, architecture-analysis, docs-and-messaging, or tooling-prompting) based on readiness and risk rules. - Repo-Aware Context Injection: Selects only the repository facts, docs, and code areas that materially change the downstream agent's first actions, avoiding generic repo dumps. - Use Case: Paste a rambling voice-transcribed bug report mentioning opencode.json and provider.gonkagate, and receive a structured bug-investigation handoff prompt with exact literals, likely code areas, and explicit open questions. ## Quick Start Ask the agent to turn your rough coding notes into a context-rich handoff prompt for the opencode-setup repository.

Frequently Asked Questions about coding-prompt-normalizer

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

FAQPage Schema
How do I turn a messy coding request into a prompt for an AI agent?

Provide the raw notes, transcript, or chat fragment and ask for a context-rich handoff prompt. The Skill removes filler and duplicates, preserves exact technical literals like file paths and commands, and outputs a structured prompt with objective, repo context, and acceptance criteria.

How does the Skill decide between implementation and investigation prompts?

It applies readiness rules: direct implementation prompts are emitted only when the change, target surface, and success criteria are clear and low-risk. Symptom-first or unclear requests default to bug-investigation, and ambiguous or product-contract changes default to planning-spec.

Can it handle mixed-language or speech-to-text input?

Yes, mixed-language and dictated transcripts are a primary use case. Technical literals are kept verbatim in any language, connective text is normalized, and the output prompt defaults to English unless another language is explicitly requested.

Does this Skill write code or specs itself?

No, it only prepares the task context and handoff prompt. Downstream domain skills such as typescript-coder or technical-design-review handle the actual implementation, review, or specification work.

What happens when a request is too ambiguous to act on?

The Skill keeps uncertainty explicit instead of hiding it behind polished wording. It emits a planning-spec or architecture-analysis handoff with short Assumptions and Open questions sections rather than inventing files or behaviors.