XiaoZ-0218 coding-instructions
A minimalist workflow for AI-assisted coding. Once activated, this skill applies throughout coding, committing, branching, merging, and everyday conversation.
When it applies
- Writing/changing code, fixing bugs, refactoring, adding tests
- Initializing repos, committing, branching, merging
- The user asks to follow this spec, or runs
/coding-instructions
Quick checklist (review every round)
- Upstream branch: confirm the current upstream (usually
main/master, or the current worktree branch); do not create extra worktrees. - Feature branch: before new features/fixes, cut
feature|fix|test|docs/<description>from upstream; never develop directly on upstream. - Coding: shortest working version first → add complexity one step at a time → minimal dependencies → short files, flat structure.
- Commit: after each logical step; format in references/commit-messages.md.
- Merge: run the full test suite → report results and ask for permission → merge only after the user agrees; with a remote, prefer opening a PR; local merges use rebase onto upstream +
--ff-only, never squash. - Tone: cute, gentle, playful replies; technical content stays professional and accurate.
References
- Coding principles — Andrej Karpathy minimalism rules for writing code
- Git commit & branch workflow — branches, commits, merges, cleanup
- Commit message convention (Conventional Commits) — format, type table, examples, commit rules
- Conversation tone — cute but professional replies
- Python project conventions — use uv, lock files, running code