aictrl

Plugin aictrl from marketplace aictrl-public in aictrl-dev/skills. Commands read from the repo's manifest — 6 days ago.

Skills (17)

• code-review

  Review the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code. Use when the user says "review this PR", "do a code review", "find defects in this change", or provides a pull or merge request identifier.

• create-bug

  Create an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement. Use when the user says "file a bug", "report this defect", "turn these symptoms into a ticket", or describes broken or regressed behavior.

• create-issue

  Create a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions. Use when the user says "create an issue", "open a ticket", "make a backlog item", or describes a feature or chore that should be tracked; delegate defects to create-bug.

• create-pr

  Draft or improve a reviewer-ready pull request title and body from an exact revision, linked issue, implementation context, and verification evidence. Use when the user says "create a PR", "draft a PR", "write the PR body", "improve this pull request description", or "update the PR title and body".

• create-workflow

  Create and validate an aictrl.dev workflow v2 YAML file with typed parameters, inline task nodes, mappings, conditions, loops, retries, triggers, and approval gates. Use when the user says "create a workflow", "write workflow YAML", "automate this engineering process", or asks for a file under .aict

• design-review

  Professional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow). Actionable, located critique against orientation, information architecture (within and across screens), primary task, visual hierarchy, friction/cognitive load, acce

• execute-workflow

  Discover, inspect, start, monitor, approve, or cancel an existing published aictrl.dev workflow with explicit authorization and durable run handoff. Use when the user says "run a workflow", "start this aictrl workflow", "monitor workflow run", "approve workflow step", or "cancel workflow run".

• explain-change

  Turn a pull request, commit range, issue, ADR, or other completed change into a repository-grounded technical explainer that teaches the design, difficult trade-offs, and current rollout state. Use when the user says "explain this change", "walk me through this PR", "what does this commit do", "docu

• implement-code-change

  Implement an engineering issue through tests, code, review, and CI, with separate story and bug paths and an optional connected aictrl.dev workflow. Use when the user says "implement issue 123", "fix this bug", "make this code change", or "take this ticket to a merge-ready PR".

• judge-review-findings

  Judge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code. Use when the user says "triage review findings", "judge these comments", "which findings are real", or "decide what to fix from this review".

• measurement-plan

  Create a measurement plan for a feature using the Goal-Question-Metric (GQM) structure — defines a measurement goal, learning objectives, metrics, and implementation (product analytics events, warehouse tables, event pipeline). Use when user says 'measurement plan', 'GQM', 'goal question metric', 'g

• recording-product-demo

  Produce a narrated product demo from a repo with a web UI — discover and boot the app locally, prep demo data and auth, prepare narration through the user's selected speech tools, record a time-locked Playwright journey, assemble a 1080p MP4 with branded cards, and build a publish kit with captions

• reply-to-code-review

  Judge current-head review findings, fix accepted defects, run verification, post evidence-backed replies, and request bounded re-review. Use when the user says "address review comments", "reply to code review", "fix accepted findings", or "get this PR through review".

• root-cause-analysis

  Perform an evidence-driven root cause analysis of an incident, recurring defect, failed release, or reliability problem. Use when the user says "perform root-cause analysis", "do a five-whys analysis", "why did this happen", "analyze this incident systemically", "why does this keep recurring", or "f

• spec-review

  Review an engineering issue or specification against repository evidence for ambiguity, missing acceptance criteria, hidden scope, test gaps, and implementation risk. Use when the user says "review this spec", "check issue 123", "is this ready to build", or "find gaps in this ticket".

• ui-polish

  Polish an existing UI screen with evidence. Renders it at phone and desktop width, measures what screenshots hide (column alignment, field widths, label placement, tap targets, input font size, contrast, overflow, dead space, distance to the primary action), judges the look against a short polish ru

• ux-testing

  Usability-test any web page or HTML prototype with AI agents acting as first-time users, then improve it in a measured loop. Tester agents drive the page through a local Playwright harness that shows them only the accessibility tree (or only screenshots, for vision testers); success is verified from

MCP servers (1)

• aictrl

  connects to: https://aictrl.dev/mcp

Similar plugins