awill1988
- 3 skills
- 0 followers
- 5 hours ago last updated
- ▌ Pr Stacks · awill1988 bundleIndex stacked pull requests across an org and write the message that asks for review — merge order, what each PR does, its tracker ticket, and where review has stalled. Renderings: a team-facing digest, a per-PR split for separate threads, and a nudge naming only what has genuinely gone quiet. Use when asked to list or summarise stacked PRs, say a stack is ready for review, chase reviewers, check what is waiting on whom, or draft a PR status update for Slack. Do NOT use for reviewing the contents of a PR, for writing a PR description or commit message, or for a single PR that is not part of a stack.
- ▌ Daily Standup · awill1988 bundleBuild a standup report for the previous working day from what actually happened — PRs authored, updated and reviewed, tracker tickets that changed state, and the coding-session nuance none of those record. Detects a gap in your own activity and switches to catch-up mode, reporting what moved while you were away instead of an empty day. Use when asked for a standup, yesterday's summary, standup notes, "what did I do yesterday", or a catch-up after time off. Do NOT use for sprint reports, retrospectives, or anyone else's activity.
- ▌ Publishing Docs · awill1988 bundleSteers the writing of technical documentation that is about to be published — design docs, decision records, RFCs, architecture pages, proposals headed for a wiki or a review audience. Restructures a draft into a register that teaches: define terms before using them, survey alternatives fairly, hedge what is unproven, and demote detail to appendices. Use before publishing, posting, or substantially rewriting any document that people beyond the implementers will read. Do NOT use for code comments, commit messages, API reference generation, changelogs, or chat replies.