preferredcredit-pci-claude-code-toolbox

Plugin preferredcredit-pci-claude-code-toolbox from marketplace cascade-code-general-misc-1 in joshuarweaver/cascade-code-general-misc-1. Commands read from the repo's manifest — 1 month ago.

Skills (21)

• create-crd-bug

  Creates a Bug in PCI's Jira CRD project (Credit Risk & Decisioning) for a defect — environment, test data, repro steps, expected vs actual, impact. Invoke when the user wants to file/report a CRD bug or something working incorrectly. Enhancement ideas → create-crd-story. Also runnable via /create-cr

• create-crd-change

  Creates a Change (release record) in PCI's Jira CHANGE project that bundles implemented work items (given explicitly and/or scraped from git commits on named branches) as Relates links, with collaborative Validation/Release/Rollback narrative. Invoke when the user wants to create a Change or release

• create-crd-epic

  Creates an Epic in PCI's Jira CRD project (Credit Risk & Decisioning) — a long-lived workstream bucket (goal, scope checklist, decision log) that Stories/Tasks/Bugs parent to. Invoke when the user wants to create/open a CRD epic or workstream grouping for a program/product phase. A single code chang

• create-crd-initiative

  Creates an Initiative in PCI's Jira CRD project (Credit Risk & Decisioning) — the top-level theme that groups Epics, in the team's standard format (goal, epic-scope checklist, out-of-scope lines, decision log). Invoke when the user wants to create/open a CRD initiative or a multi-epic theme/program.

• create-crd-story

  Creates a Story in PCI's Jira CRD project (Credit Risk & Decisioning) for a concrete code/system change — user story/goal, details, testable acceptance criteria. Invoke when the user wants to create/file a CRD story or track an implementation change. Non-code work → create-crd-task; defects → create

• create-crd-task

  Creates a Task in PCI's Jira CRD project (Credit Risk & Decisioning) for non-code work — decisions, tradeoff analysis, spikes/data pulls, AccountMate/client configuration, documentation, coordination. Invoke when the user wants to create/file a CRD task for non-implementation work. Code/system chang

• adhoc

  Scaffold a new adhoc work item under Active\<slug>\ with the standard issue shape but no Jira link. Accepts either explicit `<slug> "<title>"` or a free-form task description (slug + title are inferred and confirmed).

• author-review

  Run an author self-review before creating a PR at PCI. Gathers context, assesses complexity, runs specialized agents, and produces a structured review summary for the PR description.

• create-change-issue

  Use when creating a Jira CAB ticket in the CHANGE (Change Management) project — these tickets use a different field layout from CRD/CO. Triggers on phrases like "create a change ticket", "open a CAB", "deploy X", "Updated X", or any mention of CHANGE-#### tickets that need shaping.

• create-issue

  Use when creating a new Jira ticket in a regular project (CRD, CO, etc.) — the standard Story workflow with summary, markdown description, priority, and optional story points. Triggers on phrases like "create a story", "open an issue", "new CRD ticket", "new CO story", "file a ticket for X", "scaffo

• direct

  Open a direct-mode session on a single issue in the current chat. Workflow runs end-to-end interactively instead of via dispatched subagents.

• jira-import

  Import a Jira issue (CRD, CO, or CHANGE project) into a local Active\<KEY>\ folder by key, or browse open issues assigned to you. Trigger phrases include "import <KEY>", "pull <KEY>", "scaffold ticket", or running /jira-import with no arguments to pick from a list. Re-imports refresh the Description

• qa

  Run a QA verification pass for a Jira ticket or adhoc investigation against a deployed environment (dev, qa, or staging). Composes a scenario from how-tos and test data, drives automated steps via Chrome MCP, prompts the user for manual steps, captures evidence, and reports the verdict. No local cod

• rereview

  Re-evaluate a prior code review (AI- or human-generated, or a mix) against the latest changes and the conversation on the PR. Reads prior findings, thread replies, and the delta diff; produces an updated status per finding (addressed / still-present / acknowledged / false-positive / superseded) plus

• reviewer-check

  Run a reviewer validation check on a PR at PCI. Validates the author's AI review, runs an independent code quality pass, and identifies missed issues.

• smoke

  Run an autonomous local smoke walk over a Jira ticket or adhoc investigation. Starts the local app(s), composes a walk plan from the acceptance criteria, dispatches the playwright-driver subagent to drive the browser while tailing app logs for exceptions. Local environment only — for deployed-env QA

• status

  Discovery + housekeeping pass over <workspace>\Active\. Refresh PlanningWorkspace, sync Jira Status field on local files, sweep completed items, print dashboard (markdown + HTML), suggest next work, surface unimported Jira tickets. No dispatch.

• work

  Process go-flagged items in <workspace>\Active\, or force-dispatch a single named item. Local-first queue runner. For dashboard / sync / sweep / discovery, use /status.

• workspace-init

  Bootstrap a workspace for the engineer-toolkit plugin's Jira-driven dev workflow — checks plugin prereqs, CLI binaries (git, dotnet), prompts for user-specific config, scaffolds a small user-owned CLAUDE.md plus the plugin-managed workflow doctrine, and migrates pre-split workspaces.

• create-change-from-release

  Build the Jira Change Management (CHANGE) story for an ENTIRE Public Facing (PF) release or hotfix that is tracked as a Jira release version (a fix version). Use this when the user points at a whole release — a pasted PF release-report URL (`.../projects/PF/versions/<id>/...`), a fix-version name or

• create-pf-issue

  Creates a Story (or Task) in PCI's Jira PF project (Public Facing) with the team's full field set — Description, Technical Details, QA Details, System Component, Product Manager, QA Person. Invoke when the user wants to create, file, or write up a PF ticket for public-facing work: the client portal,

Similar plugins