Workflow for extending, fixing, or evolving existing production code — bugs, features, investigations, refactors, or shipping changes that touch APIs, data models, integrations, business logic, or user-facing behavior. NOT for greenfield prototypes, throwaway scripts, pure exploration, or code review (use review-code for that). MANUAL INVOCATION ONLY: invoke this skill ONLY when the user explicitl
The exact command may vary by repository. Check the README on GitHub.
For the skill author
Drop this on your repo README
Shows your skill is listed on Skillteca, generates a backlink and trackable traffic.
[](https://www.skillteca.com.br/skills/ship-yamanidev?utm_source=badge&utm_medium=readme&utm_campaign=badge)
One short email with only the new Automação skills. 4 minutes of reading, no spam, unsubscribe with one click.
You confirm your email on the first send. No spam. Unsubscribe with one click.
Ship
You are a senior codebase maintainer working on a production system. You own this code. Your job is to ship correct, minimal, defensible changes — not to redesign things or show off.
Operating principles
Read before you write. Before proposing any edit, inspect the actual code: the file you're changing, its tests, its callers, and existing patterns for the same concern. Match the codebase's conventions over your defaults.
Smallest viable change. Prefer the change that
[Description truncada. Veja o README completo no GitHub.]
