Git i control de versions
Operacions de Git, assistència per a commits i gestió de branques
info
osdlc
Report the runtime state of the sdlc plugin this session is actually running — the on-disk root it loaded from (CLAUDE_PLUGIN_ROOT, resolved through any symlink), the manifest version, whether it's a live working tree or a pinned cache snapshot, the git branch/commit/dirty state, and every ~/.claude/plugins registration that mentions the plugin. Read-only; for self-verifying which install won when several are configured.
task-work
osdlc
Pick up a task from docs/planning/tasks/, validate it, acquire its lifecycle lease, spin up a worktree, run the implementation-ready gate, acquire the run's phase on the lease once that gate passes, clarify open questions, implement via sub-agent (with a heartbeat thread keeping the lease alive), run local quality checks, write the handoff.md blob, transition the lease to awaiting-review, and open a PR carrying the lease-binding footer. Exits at PR open; /sdlc:pr-respond and /sdlc:task-close-out take over from there.
pr-stats
osdlc
Summarize a pull request or branch diff beyond GitHub's +/-: lines added and removed by code, comments, blank and prose; a change-category breakdown (added, deleted, renamed, tests, docs, generated, formatting-only, comment-only, logic); dependency and exported-API changes; and the cyclomatic-complexity movers. Use before or after opening a PR, in review, or when asked to "summarize this change", "how big is this PR", "what did this branch actually change", or "add stats to the PR". Optionally writes the table into the PR body. Runs from a bundled script with plain Node, git and gh; needs no other plugin.
session-cleanup
osdlc
Tear down the branch and worktree a conversation worked in, but only after proving the work landed: nothing uncommitted, nothing unpushed, and the branch merged (squash merges included). When that fails it reports what is unlanded and stops without touching anything. Invoke at the end of a session for "clean up", "clean up this branch", "we're done here", "tear down the worktree", or "is this safe to delete".
backlog-triage
osdlc
Walk untriaged backlog files in docs/planning/backlog/ and decide what to do with each: promote to task, promote to milestone, close, defer (bump last_reviewed), or leave it for an open PR. Before each decision, checks the item against main: the code it names, merged and open PRs, and existing planning entities, and recommends an action with quoted evidence. Promotion calls sdlc task create / sdlc milestone create directly, or points at existing work that already covers the item, and updates the backlog frontmatter to match. Commits each decision atomically on the current branch, honouring the project's branching conventions.
task-close-out
osdlc
Close the loop on a task whose PR has merged: flip the task file to state: closed/done on main with a completion_note citing the merged PR, then tear down the task's worktree and its task/<basename> branch (local and origin) through the safe cleanup ops (sdlc project cleanup and apply-cleanup), which leave a receipt. Detects the merged PR automatically from the branch name (override with --pr <N>). Emits a deterministic stdout marker so /sdlc:orchestrate can dispatch on the result.
import-planning
osdlc
Walk a project root for planning-shaped prose (READMEs with roadmap sections, brain-dump notes, dated checklists, issue archives, etc.) and produce draft task/milestone entities under docs/planning/, so a project can adopt the SDLC plugin without re-keying its prior planning history. Spins up a fresh worktree, runs a deterministic scanner, dispatches one sub-agent per candidate to interpret it, presents a batched plan for one-shot approval, then shells out to sdlc task create / sdlc milestone create and Edits the drafted body sections in. Opens a PR at the end. Pass --auto to skip the confirmation prompt, --dry-run to stop at the plan, --scope <path> to restrict the scan.
check-pr
osdlc
"Tend one or more pull requests in a single pass: report their state, rebase them onto their base branch when they are behind or conflicting, and assess and answer new review comments. Fixes worthwhile comments straight away with --fix auto, or proposes the fix and waits for a thumbs-up with --fix ask (the default). Keeps no files of its own and records its answers to review-pr findings on a state ref beside the PR, so it suits a loop such as /loop /check-pr."
capability-map
osdlc
Map out the capability graph for one scope of the project: survey the code (or the product's capability-map table), propose new Capability entities where the map has gaps, enrich existing ones with locations, grain, audience and related links, and report retire candidates. Runs sdlc capability coverage and sdlc capability graph read-only, dispatches one read-only sub-agent per candidate, renders one batched plan for approval, then writes through sdlc capability create / sdlc capability update and opens a PR. Invoke when capabilities are missing, ungraded, unanchored, or when the System page's capability view looks empty for an area. Usage: /sdlc:capability-map <dir C-NNNN areas> [--dry-run] [--auto].
lib-publish-ready
osdlc
Audit one library package for a first public release. Produces a readiness report (every quality-bar row with evidence and a verdict: pass, gap, blocker, n/a or owner), the evidence for the name, worthwhile, stable, home and API gates, an inventory of the public API, the first public version, a sanitized CHANGELOG draft, owner questions with a recommendation each, and a fix list whose items are tagged safe or needs-decision. Reads the package; never writes inside it. Use it before publishing a library to a public registry such as crates.io or npm, or to re-audit after fixes.
spawn-task-pr
osdlc
Open a PR carrying a single scaffolded follow-up task file on a target repo. /sdlc:task-work Step 8 runs the spawn-from-post-mortem procedure, whose step 4 dispatches one invocation per classified friction bullet, so each follow-up lands as its own PR. Upstream-plugin / Cross-project-request bullets target the resolved foreign repo; Local bullets target this repo. Idempotent and non-interactive: takes the target-repo path, slug, headline, classification, and tag; reuses or creates a worktree on that repo; branches from origin/main (--target-base default main, --target-remote default origin); scaffolds the task via sdlc task create at the fallback status (default planning/draft); optionally drives it to open/ready via auto-define + ensure-ready when --drive-to-ready is set; commits on --branch (default meta-task/<slug>); pushes; and per --pr either opens a fresh PR or appends to that branch's open rolling PR. Emits a deterministic stdout marker. --no-push rehearses without pushing or opening a PR.
migrate-runtime-state
osdlc
Move SDLC-plugin runtime state from the legacy .claude/ location to .sdlc/ in a consuming project (worktrees, pr-cursors, orchestrator-log). Idempotent — re-running on an already-migrated project is a no-op. Operates directly on the main repo, since the things being moved are worktrees.
task-auto-define
osdlc
Drive one or more task documents toward the implementation-ready contract (solutions/ontological/lib/model/entities/task/implementation-ready.md) by synthesizing best-effort content from each task's existing prose plus codebase context, without prompting the user. Multiple tasks run in sequence, one commit and one slug-namespaced terminal marker each. --make-pr pushes the run's commits on a chore/ branch and opens a PR (default off — commit on the current branch only). Stamps a discoverable machine-authored marker on every synthesized spec. Never changes state: /sdlc:task-ensure-ready promotes to open/ready and stamps readiness_verified_at in one commit. Dispatched by /sdlc:task-ensure-ready when a task is autonomy: autonomous/pr and the deterministic verify reports a gap.
bug-finder
osdlc
Sweep an entire codebase for real bugs and fix them. Partitions the tree into module-boundary territories, then runs three chained agent workflows — scan (three altitudes: in-function, in-module, in-library) → adversarial validate → fix → verify-fix → land — so a fresh agent performs every step and the orchestrating session never reads source itself. Opens one PR per module boundary, then surveys the open PRs, computes the conflict matrix deterministically with git merge-tree, and merges the overlapping bugfix branches into each affected PR in a single aggregated push so CI runs once per PR, not once per fix. Pass --bomb for maximum parallelization.
milestones-from-file
osdlc
Given a filepath, do a best-effort extraction of milestone entities from that file (markdown notes, planning docs, brain-dump, anything). Creates one milestone file per extracted candidate via sdlc milestone create, all inside a fresh worktree, then opens a PR. Pass --auto to skip per-candidate confirmation.
project-cleanup
osdlc
Sweep local branches, worktrees, remote branches, and SDLC task linkage to identify what can safely be cleaned up. The deterministic sdlc project cleanup scanner gathers facts and pre-classifies each item; this skill dispatches sub-agents in parallel to investigate ambiguous cases, then presents a single batched plan for one-shot approval, then hands the approved rows to sdlc project apply-cleanup.
task-ensure-ready
osdlc
Verify a single task document against the implementation-ready contract (solutions/ontological/lib/model/entities/task/implementation-ready.md). Writes frontmatter only, leaving body content to /sdlc:task-define. On pass, stamps readiness_verified_at on frontmatter. On fail, clears that stamp, records a definition_gap, and downshifts state to planning/needs-definition — except when the input is already in-progress or in-progress/blocked, in which case state is preserved (the task is mid-flight and a downshift would corrupt task-work state). When the task is autonomy: autonomous/pr and the deterministic verify finds a gap, it dispatches /sdlc:task-auto-define once to best-effort fill the gap, then re-verifies, self-readying the task. Dispatched by /sdlc:task-work Step 5a after the readiness gate, and runnable standalone. Idempotent and safe to re-run.
openbook
josephliver623
Search and browse real-time Signals about places and businesses on OpenBook. Help users publish Signals when they want to share a change, observation, or tip about a place (price change, closure, new opening, quality shift, recommendation). Signals are lightweight, time-stamped facts — the "changelog" of the physical world. Always confirm with the user before publishing.
stop-slop-quality
strikersam
Remove AI writing tells and cliches — enforce natural, human-quality output
workflow-execute-plans
Heyvhuang
"Execute written implementation plans: first read and critically review the plan, then implement in small batches (default 3 tasks), produce verification evidence per batch and pause for feedback; must stop immediately and ask for help when blocked/tests fail/plan unclear. Trigger words: execute plan, implement plan, batch execution, follow the plan."
review-quality
Heyvhuang
"Unified codebase quality review: merge readiness verdict + maintainability (Clean Code) + docs-vs-code consistency. Use for code review, quality check, refactor check, outdated docs check, or merge/production readiness."
review-merge-readiness
Heyvhuang
"Request/execute structured code review: use after completing important tasks, at end of each execution batch, or before merge. Based on git diff range, compare against plan and requirements, output issue list by Critical/Important/Minor severity, and provide clear verdict on merge readiness. Trigger words: request code review, PR review, merge readiness, production readiness."
workflow-execute-plans
Heyvhuang
"Execute written implementation plans: first read and critically review the plan, then implement in small batches (default 3 tasks), produce verification evidence per batch and pause for feedback; must stop immediately and ask for help when blocked/tests fail/plan unclear. Trigger words: execute plan, implement plan, batch execution, follow the plan."
review-merge-readiness
Heyvhuang
"Request/execute structured code review: use after completing important tasks, at end of each execution batch, or before merge. Based on git diff range, compare against plan and requirements, output issue list by Critical/Important/Minor severity, and provide clear verdict on merge readiness. Trigger words: request code review, PR review, merge readiness, production readiness."