Software-engineering workflow skills: diagnose bugs from tickets, specs, or a description down to their root cause, turn a design conversation into a spec file, plan how to build a spec, tickets, or an agreed design against the real code, step by step with the test each step writes first, implement it with the session's model orchestrating worker subagents on a cheaper model, review code for correctness, the repo's written standards, and conformance to a spec, then commit with staging and message conventions and write the PR title and description.
Commit changes: stage the task's files by name, write the message, and run the commit. Use whenever the user asks to commit changes, make a commit, or write a commit message, even if they don't mention staging or formatting.
Pinned to revision e88ad6d185e8, so it is the text this page describes rather than whatever the author pushed since.
Every link opens the file at its source, pinned to the revision this page describes.
