AlexHagemeister
- 11 skills
- 0 followers
- 18 hours ago last updated
- ▌ Help Gnadd · alexhagemeisterGNADD workflow orientation: GitHub issues as backlog, describe-vs-track file rule, and which GNADD skill handles each workflow step. Use when the user asks about GNADD, agent-driven development workflow, project context files, tasks.md versus issues, startup guidance, how to set up work, or how to install, update, or refresh the GNADD skills themselves. Do not use for routine coding unless the question is workflow-shaped.
- ▌ Init Gnadd · alexhagemeister bundleBootstrap a project onto GNADD using the bundled gnadd script and gh: turn on the server-side rails (squash-only merges, PR-required main), write the agent-agnostic conventions file (AGENTS.md) that points agents at GNADD and carries the preview launch line, land init's own files on main through a PR, and report what was set up and what is still the user's to do. Safe to rerun. Use when the user wants to set up a new repo for GNADD, initialize the workflow, or add the rails and conventions to an existing repo.
- ▌ Yolo Gnadd · alexhagemeister bundleAutonomously run the full GNADD loop on one already-decided unit of work: an open issue number (issue loop) or a trivial-change description (quickfix flow), end-to-end through merged-on-main, synced, and cleaned up, with no human intervention unless a real blocker halts it. Includes an independent review pass on the PR before merging. Use when the user says yolo, wants an issue or quickfix taken all the way to merged without further prompts, or delegates a decided piece of work end-to-end.
- ▌ Audit Gnadd · alexhagemeisterRead-only GNADD alignment audit: load workflow principles, scrutinize context files for describe-vs-track violations, perform a shallow git/workflow check, and return a severity-grouped report with minimal proposed fixes. Nudges /new-issue-gnadd for remediation slices; never edits files or creates issues. Use when the user asks to audit GNADD alignment, review workflow hygiene, check project context files, or find describe-vs-track violations.
- ▌ Prime Gnadd · alexhagemeister bundleOrient a new chat session with a read-only project snapshot using the bundled gnadd script, git, and gh: project shape, current branch state, whether main is behind or diverged from origin, stashes, recent commits, open issues, open and merged PRs, and active issue context. Fetches latest remote state first. Use when the user asks to inspect project state, orient a session, see what work is open, or decide what to do next.
- ▌ Commit Gnadd · alexhagemeister bundleMake atomic git commits during active development. Use when the user invokes /commit-gnadd or asks to commit, save progress, checkpoint work, or create a git commit; reviews changes, confirms staging, writes a conventional commit message, creates the commit, and reports the result.
- ▌ Vision Gnadd · alexhagemeisterWrite or revise a project's VISION.md through an interview: the user brain-dumps an idea, the agent sorts it by commitment level (Core, Possibility space, Open tensions) in the user's own confirmed words, and writes the file in the shape GNADD.md defines. Rerunning on an existing VISION.md revises it in conversation and preserves what the user does not change. Use when the user wants to write a vision, capture the intent behind a new project, start VISION.md, or revise the one they have. Never produces a plan, roadmap, or spec.
- ▌ Quickfix Gnadd · alexhagemeister bundleLand a trivial change on main through a PR in one flow using the bundled gnadd script and gh: no GitHub issue required — the PR is the record. Branch off synced main, commit, push, PR, wait for CI, squash-merge, sync main, and clean up. Refuses oversized or mechanics-touching changes with a redirect to the full loop. Use when the user wants to quickfix, quickly land, or ship a small change — a typo, one-line doc fix, or tiny tweak — without opening an issue.
- ▌ New Issue Gnadd · alexhagemeisterDraft GitHub issues from natural language descriptions. Use when the user describes new work, asks to capture a backlog item, or needs a behavior-focused GitHub issue; interviews for requirements as needed, confirms the draft, and creates the issue via GitHub CLI after approval.
- ▌ Start Issue Gnadd · alexhagemeister bundleSet up work on a GitHub issue using the bundled gnadd script and gh: identify the issue, protect any in-progress work, resume or create the issue branch, load the issue spec, propose an implementation plan, and wait for user approval before coding. Use when the user wants to begin or resume work from an open GitHub issue, switch into issue work, or turn an issue into an implementation session.
- ▌ Resolve Issue Gnadd · alexhagemeister bundleWrap up work on a GitHub issue using the bundled gnadd script and gh: identify the issue branch, verify the work against acceptance criteria, run the project's tests, commit final changes, create or resume the PR, check mergeability and CI, optionally merge, sync the issue record, and clean up. Does not rebase. Use when issue work appears complete, the user wants to ship an issue branch, or the next step is verification, PR creation, merge decision, and cleanup.