Skip to content

alisterpineda/swe

v4.0.0MIT

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.

GitHub
skills

pr-writeup

Write a pull-request title and description for a branch's net change and print them for pasting; it doesn't open the PR. Use whenever the user asks for a PR title, description, or write-up, or needs the text for a PR they're about to open, even casually ("write me a PR", "what should the PR say"). Not for summarizing or reviewing a PR that already exists.

Read SKILL.md at the source

Pinned to revision e88ad6d185e8, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.