repo-workflow-conventions
Installation
SKILL.md
Repo Workflow Conventions
Overview
This developer's personal conventions for repository hygiene: where team-shared vs. personal-only files live, where ephemeral workflow artifacts go, and how branches/commits are structured. Independent of stack — applies to any git repository.
Quick Reference
| Concern | Rule |
|---|---|
| Personal note vs. shared rule | *.local.md (gitignored) vs. plain *.md (tracked, team-shared) |
| Where a personal note lives | Same path as its shared counterpart, .local.md before the extension — or topic-named if there's no counterpart |
| Ephemeral workflow artifacts (reports, reviews, logs) | Typed tmp/ subfolders — never the repo root or .git/ |
| A plan/spec document produced by a planning skill | Project root as YYYY-MM-DD-<name>.md, deleted once implemented and no longer needed |
Committing to main |
Never — always branch first, even for a one-line fix |
When git commit runs |
Only on explicit user request — never automatically after a task or plan |
| Commits per feature | One, at the end — no intermediate commits per task |
| Commit message | Past tense, one line, no body, no co-author trailer |