chris-peterson

commit

Stage changes, run tests, review, then commit and push. Use when work is ready to commit or push.

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.

issues

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.

Data & Documents Listed

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 an MR/PR 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.

AI & Automation Listed

tack

Track AI-assisted development work with the `tack` route tracker, spanning session boundaries. This skill should be used at session start 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.