Review upstream releases (pi, pi-subagents, pi-mcp-adapter) over a given time frame and assess each changelog entry's impact on this project — bugs worth picking up, features that unblock work, and contract drift that could break us silently.
★not rated 28▲
+1
changed 3d agoA52 tokens
originalMIT
Drive every open Dependabot PR to main, one at a time — sync from main via GitHub, wait for its checks (fixing failures until green), squash-merge, wait for CI on main, then move to the next PR. Invoke manually.
Create a ready-to-use git worktree for the current repository at /src/ - on a new branch features/ , branched from a freshly fetched origin/main, then run the repo's scripts/init.sh in it so dependencies, skills, and agent tooling are installed. Use when the user asks to create a new workspace, worktree, or…
After a PR is opened (e.g. by /gsd-ship), drive it to a clean state -- pass the project's review skills and the pr-review-toolkit review, then get the SonarQube PR quality gate green, and, when the branch ships a GSD milestone, close that milestone last so the planning records describe the final head -- with the heavy…
Research Claude Code plugin-system behavior before discussing pi-claude-marketplace choices, then anchor recommendations and CONTEXT.md decisions to verified upstream evidence.
Start a new GSD milestone labeled with a kebab-case name instead of a version number, with phase numbering restarted at 1, via GSD's /gsd-new-milestone command. Use whenever the user asks to start, open, or begin a new milestone in this repo, asks to run /gsd-new-milestone, or invokes /new-gsd-milestone -- even if…
How to write CHANGELOG.md entries in this project -- one reader-facing bullet per pull request, its shape, wording, credits, and references. Use when adding or changing an entry in CHANGELOG.md.
How to commit in this repository -- message format, focused checks while editing, pre-commit fixers, the commit hook's npm checks, and what to do when the hook fails. Apply before every commit.
How to change README.md and its localized copies (README..md) in this project -- the writing pass every passage gets and the rule that keeps translations in sync. Use when adding or changing text in README.md or any README..md.
TypeScript style for this project -- the Google Style Guide rules the toolchain does not enforce, the comment and test-title policy, and how to review against them. Use when writing, changing, or reviewing any .ts file.
Unit test rules for this TypeScript project -- which test modules exist, how source is shaped for them, how cases, doubles, and boundaries are written, and how to review them. Use when planning, writing, changing, or reviewing extensions/pi-claude-marketplace//.ts or test//.ts.
Rules for the cucumber behavioral tests under features/ -- which files exist and how they are named, how feature files and step definitions are written, the per-scenario world, stand-ins for external services, and how to review the suite. Use when planning or changing user-visible command behavior, and when planning…
★not rated 28▲
+1
changed 3d agoA78 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: