vsdudakov
UserTurn a tracker ticket into a reviewed, QA-verified pull request. AI coding-agent pipeline of eight roles — plugin for Claude Code, Codex and Cursor.
Categories
Indexed Skills (22)
cross-repo
Features spanning several repos — dependency order, when work can run in parallel, how a shared library's release gates its consumers, and how the PRs link.
demo-prep
Builds the demo integration branch — reset it from the default branch, merge the demo-labeled PRs in a conflict-minimising order, deploy, and prepare the team notification.
develop-flow
The full pipeline from ticket to merge-ready PR — bug tickets reproduce first, feature tickets plan first, then parallel dev, internal review loop, unit tests on the change only, QA before/after on the local stack, release, CI.
fix-pr
Fixes an open PR — either what you asked for in words, or every unresolved review comment on it — through the owning dev roles, then re-reviews, re-tests, pushes to the same branch and answers every thread.
implement-change
Implements one repo's part of an approved plan in its own worktree, with unit tests written but not run, ending at the profile's verification commands — no commit, no PR.
internal-review
Reviews the local branch diff before QA and before any push — catches layering, coverage, style, and hygiene defects that QA cannot see. Posts nothing outside the workspace.
memory
Dated, provisional observations about the workspace — what happened, when, what it cost, and when an entry graduates into a rule or is deleted.
plan-review
Reviews the architect's plan before any code is written — by a different model family than the one that wrote it — and loops it back until the plan is sound. Replaces the human approval gate.
plan-template
The structure of an approved plan — problem, numbered requirements, repo order, pinned contracts, per-repo work breakdown, test plan, risks and open questions — and the shorter bug brief the reproduction path writes instead.
pr-review
Reviews an open PR in an isolated worktree and posts one review comment. Read-only and lint-only — never runs tests, edits code, or merges.
qa-verify
Verifies a change on the real local stack — browser E2E with before/after GIFs for frontend work, API calls plus datastore checks for backend work — and returns proofs and a Pass/Fail verdict.
release-cut
Cuts a periodic release end-to-end — promote the previous pre-release, branch, pre-release, notes, QA plan, deploy to the pre-production environment, prepare the announcement.
release-notes
Generates a release's notes from the diff against the previous release branch — dedup by patch-id, label cross-check, classification, QA blocks, and a generation-notes audit trail.
release-pr
Ships one repo — profile-compliant commit, push, PR from the team template with proofs, ticket attachment and comment (plus a transition where the profile declares one), then PR review and worktree cleanup.
run-unit-tests
Runs only the unit tests the change developed — plus the existing ones directly tied to the changed sources — one parallel lane per area, and routes every failure back to the owning dev role.
scratchpad
The handoff files roles write to each other during one ticket — plans, work logs, review, test and QA reports, and the proof artifacts the PR carries.
spike
Investigates a ticket read-only and produces a reviewed implementation plan — the pipeline's planning half, stopped before any code is written.
tracker
Working with the issue tracker — verifying auth, reading a ticket, commenting, transitioning, attaching proofs, and linking the branch and PR to the ticket.
workspace-setup
Creates a workspace — the .troika directory, its settings, and the profile every other procedure reads — by investigating the repos first and asking only what they cannot answer.
worktree
The one-worktree-per-branch convention — the base ref, creation, dependency wiring, the naming contract QA and release depend on, and cleanup.
pr-template
How to fill the workspace's PR body and title honestly — section by section, with the rules for a repo's own template and for stripping AI product names.
ticket-intake
Turns a short request into a well-shaped tracker ticket, or reshapes an existing one — written once, with the original description preserved.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.