as-fix
Fix
Purpose
Resolve concrete bugs safely through structured diagnosis, minimal fixes, and verification.
This skill is for bug-fix execution when scope is clear and risk is manageable.
Scope Gate (Required Before Starting)
Use this skill only when all conditions below are true:
-
Concrete issue signal exists
- Clear failing behavior, error, or regression is identified
- Enough evidence exists to begin diagnosis (logs, stack trace, failing test, or reproducible steps)
-
Likely localized fix path
- Issue appears constrained to a small area
- No expected cross-system redesign or migration
More from buiducnhat/agent-skills
write-plan
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use when scope is large, requirements are mostly known, and work should be broken into validated phases before execution.
378execute-plan
Execute an approved implementation plan exactly and safely. Use when a plan already exists and work must be carried out phase-by-phase with verification checkpoints, status tracking, and final execution reporting.
376brainstorm
Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding.
342docs
Create or refresh project documentation in `docs/`. Use when a project needs docs initialized or existing docs synced to the current codebase.
334quick-implement
Rapid implementation for small, low-risk, well-defined changes. Use when the task is narrow in scope, has clear acceptance criteria, and can be completed safely without a formal multi-phase plan.
331ask
Structured clarification and requirements gathering through focused dialogue. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
193