ds

Plugin ds from marketplace devstride in devstride/claude-plugin. Commands read from the repo's manifest — today.

Skills (31)

• plugin-release

  Cut a release of this plugin: `prepare [major|minor|patch]` validates, moves the CHANGELOG, adds the cost table, bumps the version and README line and commits `release: v<version>` on the release branch; `merge <pr>` merges a clean, green pull request under the owner's standing yes and leaves the au

• branch-feature

  Create a new feature branch off develop with proper naming convention

• branch-hotfix

  Create a new hotfix branch off a fresh copy of the production branch, for urgent fixes that must not carry unreleased work

• build-item

  Orchestrate one DevStride work item end-to-end: select, branch, build, review, merge, and completion ritual — epic stories batch onto the epic's integration branch in fast develop mode (local engines, no per-story PR) and the fully-reviewed epic release PR carries them to develop; one-off items ship

• ci-audit

  Measure executed CI minutes, premature runs before the final reviewed head, per-workflow PR reruns, post-merge pushes, and release-PR churn. Read-only; GitHub Actions via gh.

• classify-release

  Step: ask the repository's release.classifySkill whether a release is light or full; anything but a clear answer is FULL.

• comprehend-plan

  Recursively read a DevStride plan (descriptions and comments, every level) to build full grounded context before editing it or answering where it stands

• create-defect

  Create a Defect (inbound bug report / ad-hoc fix not in a sequenced plan), place it on a board, assign it to the current user, then deliver it once through the build-item loop; `deferred <item#>` parks a bug finding in the plan root's deferred container instead, never built

• create-story

  Create a one-off Story (inbound request / ad-hoc work not in a sequenced plan), place it on a board, assign it to the current user, then deliver it once through the build-item loop; `deferred <item#>` parks a follow-up in the plan root's deferred container instead, never built

• doctor

  Diagnose delivery-loop prerequisites read-only — environment, plugin, DevStride, config, CI, merge gates, docs and the Active Agents board — then offer only approved safe repairs.

• insert-defect

  Insert a new Defect into a live DevStride roadmap, spliced into the dependency chain and dated for the build-item loop

• insert-story

  Insert a new Story into a live DevStride roadmap, spliced into the dependency chain and dated for the build-item loop

• lease-checkout

  Step: lease one checkout of the repository's pool through its pool.checkout command, and print one verdict; build-item calls it first.

• local-environment

  Step: run one localEnvironment command (create, recreate, migrate, seed, teardown or name) with its placeholders filled, and print one verdict.

• plan

  Drive a high-quality DevStride plan into existence under a parent item through an interactive discovery loop with the user

• post-deploy

  Step: run the post-deploy health hook (release.postDeployCheckSkill) in check or close-out mode and pass its verdict through; release calls it.

• pr

  Open a draft pull request for the current branch, run the full review-and-settle loop, and optionally link the PR to its DevStride item

• pre-merge-check

  Step: ask the repository's release.preMergeSkill whether production needs anything before the release merges, and print one verdict.

• pre-ship

  Step: select or run the repository's local pre-ship checks (preShipChecks) for a pull request or a release, and print one verdict.

• push

  Stage, commit, type-check, and push the current branch following repo commit conventions

• rationalize-gantt

  Backfill synthetic dates and rationalize the dependency graph of a DevStride plan so its Gantt renders as a clean cascade

• rebalance

  Re-slice a live DevStride plan's not-started leaves to a different delivery profile in place — merge or split them to the new grain, preserve every absorbed spec, re-wire the dependency chain, and re-date — without re-planning from scratch

• release

  Promote the release source branch to production — the release that triggers the repo's production deploy: cut the release PR, run the full gated review, update documentation through the repo's registered local docs skill, merge to production on explicit owner go-ahead, and write release notes only w

• return-checkout

  Step: return a leased checkout through the repository's pool.checkin command when the run ends or hands over, and print one verdict.

• review

  Run a PR through every configured review engine (as configured in `review.*`), address every verified finding, resolve the addressed threads, release CI and settle it green, then report or notify

• setup

  Set the delivery loop up for this repository — inspecting it for everything answerable without asking (package manager, verify commands, CI provider and draft gating, branches, review engines), mapping your DevStride work types onto the loop's roles, asking only about what is left, and writing .clau

• sync-knowledge-base

  Step: run the knowledge-base sync hook (docs.knowledgeBaseSyncSkill) after documentation was published live, and print one verdict; release calls it after docs.

• ultracode-build

  Build engine for a scoped DevStride story: understand, build, verify, and run a risk-sized pre-handoff check

• update-docs

  Step: run the repository's documentation hook (docs.updateSkill) once — update or check — and print one verdict; release and build-item call it.

• update

  Update the exact DevStride plugin installation that loaded this command to the latest published version, verify the installed copy, and explain when to reload. Use only when the user directly invokes /devstride:update or explicitly asks to update the DevStride plugin now.

• write-release-notes

  Step: run the release-notes hook (docs.releaseNotesSkill) in publish or draft mode, only when the owner asked, and print one verdict.

MCP servers (1)

• devstride

  connects to: https://api.devstride.com/mcp

Hooks (18)

• SessionStart

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/version-check.sh"

• SessionStart

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-title.py" hook; exit 0

• SessionStart

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-runtime.py" record; exit 0

• SessionStart

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• UserPromptSubmit

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-title.py" hook; exit 0

• UserPromptSubmit

  bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-gate.sh"

• UserPromptSubmit

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-runtime.py" prompt; exit 0

• UserPromptSubmit

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• PreToolUse

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-runtime.py" seen; exit 0

• PreToolUse

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• PostModelSwitch

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/session-runtime.py" seen; exit 0

• PostToolUse

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• PostToolUseFailure

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• PostToolBatch

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• Notification

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• Stop

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• StopFailure

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

• SessionEnd

  command -v python3 >/dev/null 2>&1 && python3 "${CLAUDE_PLUGIN_ROOT}/hooks/presence.py" hook; exit 0

Similar plugins