chris-peterson

beacon

Label a session's project/task on the iTerm2 tab, and check the beacon CLI wrapper is current on first use per session.

1 Updated today

List and rank the forge issues assigned to you so you can pick what to work on next — ranked by soonest due date, then most recently updated. Use whenever finding, browsing, surveying, or choosing the next issue/ticket to pick up, even when the user doesn't say "issues" — e.g. "what's next?", "what should I work on?", "anything due soon?", "show my open tickets". For filing or updating a single issue, use the `issue` skill instead.

commit

Stage changes, run tests, review the diff and drafted commit message with the user, then commit and push once they approve. Use when work is ready to commit or push; the diff review is a step of this skill, so don't offer to show the changes as a separate step beforehand.

issue

File a new forge issue (or update an existing one) that leads with WHY the work is needed. Use when filing, creating, drafting, or updating a single issue or ticket. To find, browse, or pick which issue to work on next, use the `issues` skill instead.

pipeline

Report a commit's forge pipeline state, or watch until it settles. Use when checking the status of a pipeline, build, CI, or GitHub Actions run — or watching one to completion.

prepare-review

Open the PR/MR on an already-pushed branch, rebase on the default branch if behind, and draft a description that tells reviewers WHY the change exists. Use when opening a PR/MR or creating a review.

resolve-feedback

Fetch an open CR's review feedback and drive each thread to resolution — fix, reply, resolve. Use when addressing review feedback or resolving comment threads on an open PR/MR.

merge

Merge an approved change request once its gates are green — waiting on the pipeline if needed — then clean up the branch. Use when merging or landing a PR/MR.

release

Cut a release for what has landed — recommend a semver bump, draft the notes, and drive the repo's own publish path. Use when releasing, publishing, cutting a version, or shipping a new version.

AI & Automation Listed

tack

Track AI-assisted development work with the `tack` route tracker, spanning session boundaries. This skill should be used to answer "what am I working on?" and load context on current work, and when the user refers to tack routes, tacks, or recording a PR/MR deliverable against tracked work. Opening and closing a session belong to the start and end skills.

0 Updated 1 weeks ago

end

Close a work session: read what actually landed, refuse to close on work that isn't durable yet, record the deliverable on the tack route, hand off the retro, and report the commands still owed rather than sequencing them. Triggers on "wrap up", "all done", "close this out".

0 Updated 1 weeks ago

start

Open a work session: read the linked issue or CR thread in full, derive one slug, cut the branch, and bind the tack route. Triggers on "start work on <issue-url>" or "pick up #42".

0 Updated 1 weeks ago