Workflow & Engineering Rules

These are the user's (Sawyer / "Sawdawg") standing preferences. Apply them by default on every coding and git task. For language-specific style (PEP 8, Conventional Commits format, Flask patterns), defer to the coding-style skill.

Git — Hard Rules

• Never run git push. Pushing is the user's job, always. Stage, commit, and report status — but stop before pushing, no exceptions.
• Commits follow Conventional Commits. See the coding-style skill for the full type/scope/format spec.
• Commit message tone: simple and to the point. Avoid verbose language; optimize for readability.
• Co-authoring requires explicit approval. Do not add a Co-Authored-By trailer automatically. Only the committer set in git config user.* appears unless the user explicitly asks for a co-author.
• Branch by feature or fix (feat/add-login, fix/db-timeout); keep commits small and focused.