dev-workflow

Plugin dev-workflow from marketplace zweihander in Alex-Kopylov/zweihander. Commands read from the repo's manifest — 25 days ago.

Skills (17)

• approve-pr

  Use when the user explicitly asks to approve and merge a pull request or merge request.

• commit

  Commit staged changes following Conventional Commits v1.0.0. Activate when user asks to commit, create a commit, or says /commit.

• create-pr

  Create a pull request from the current branch. Activate when user asks to create a PR, open a pull request, submit for review, or says /create-pr.

• dispatching-parallel-agents

  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

• pr-address-comments

  This skill should be used when the user asks to "address PR comments", "fix PR feedback", "resolve PR threads", "handle review comments", "address review feedback", "respond to PR comments", "fix code review comments", "fix what reviewers said", "work on PR comments", "iterate on PR", or "rework PR"

• pr-checkout

  Switch to PR branch from your platform. Activate when user provides a PR — ID, number, or URL — and wants to checkout/switch/review that branch.

• pr-comment

  Post a review comment to a pull request. Use whenever the user asks to "post a comment", "add review comment", "comment on PR", "leave feedback on PR", "post inline comment", "add PR note", "review comment", or wants to post any kind of feedback to a pull request. Handles both general PR comments an

• render-diff-html

  Render git diffs and file-to-file comparisons as HTML or JSON reports with diff2html-cli. Use when the user asks to get, render, open, export, or show a visual diff; compare staged, unstaged, working tree, commit range, or last commit changes; convert a patch or .diff file; or show differences betwe

• requesting-code-review

  Use when completing tasks, implementing major features, or before merging to verify work meets requirements

• spec-contradiction-hunter

  This skill should be used when the user wants to "find contradictions", "check consistency", "validate my spec", "cross-check requirements", "spot inconsistencies", or has provided a body of information (spec, requirements, design doc) that needs consistency validation. Spawns parallel agents to hun

• spec-interview

  Use when the user wants an in-depth requirements interview that produces a detailed implementation spec.

• systematic-debugging

  Use when debugging a software, DevOps, infrastructure, networks, environment related problems before proposing a fix

• ticket-branch

  Create git branch from a ticket. Activate when user provides a ticket ID or URL from your issue tracker and wants to create a branch.

• ticket-comment-status

  Post a status update comment to a work item or issue. Activate when user asks to update a task, write a status comment, post progress, or says /ticket-comment-status.

• verification-before-completion

  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

• version-bumper

  Bump version strings in project, package, plugin, and marketplace files. Activate when user asks to bump version, release, or resolves a merge conflict in version strings.

• yolo-push

  Run a guarded commit-to-deploy workflow that verifies branch freshness, invokes commit and create-pr, waits for green CI, invokes approve-pr, monitors CD, offers to clean up the merged branch and worktree, and reports final deployment state.

Subagents (4)

• ambiguity-contradiction-hunter

  Hunt for hidden contradictions behind vague language, ambiguous terms, and assumption gaps in user-provided information. Use as part of the spec-contradiction-hunter skill workflow.

• release-manager

  Use this agent when the user wants to bump the version, commit staged changes, or do both. Delegates to version-bumper and commit skills.

• structural-contradiction-hunter

  Hunt for deeper structural and logical inconsistencies in user-provided information. Requirements that are technically incompatible, scope mismatches, and implicit assumption clashes. Use as part of the spec-contradiction-hunter skill workflow.

• surface-contradiction-hunter

  Hunt for obvious, direct contradictions in user-provided information. Statements that explicitly conflict with each other. Use as part of the spec-contradiction-hunter skill workflow.

Similar plugins