AICtrl

What you can ask

• Turn this request into an implementation-ready issue.Copy

  Example path list_pr_findings→get_started · Create pr skill

• Implement this issue and prepare a merge-ready pull request.
• Review this pull request at its current head revision.

MCP connector

Server URL

https://aictrl.dev/mcpCopy

Login

OAuth

Tools

Skills

16 in the ChatGPT listing

• Code reviewReview the exact head revision of a pull request for actionable correctness, security, reliability, performance, and test findings without modifying code.
• Create bugCreate an evidence-backed bug report with reproduction, expected and actual behavior, impact, code context, and a regression-test requirement.
• Create issueCreate a code-grounded engineering story or task with scope, acceptance criteria, test expectations, risks, and open questions.
• Create prDraft or improve a reviewer-ready pull request title and body from an exact revision, linked issue, implementation context, and verification evidence.
• Create workflowCreate and validate an aictrl.dev workflow v2 YAML file with typed parameters, inline task nodes, mappings, conditions, loops, retries, triggers, and approval gates.
• Design reviewProfessional design review of any UI — a marketing page OR a product internal (dashboard, table, list, detail view, settings, a flow).
• Execute workflowDiscover, inspect, start, monitor, approve, or cancel an existing published aictrl.dev workflow with explicit authorization and durable run handoff.
• Explain changeTurn 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.
• Implement code changeImplement an engineering issue through tests, code, review, and CI, with separate story and bug paths and an optional connected aictrl.dev workflow.
• Judge review findingsJudge untriaged code-review findings for the current pull-request head as TRUE, FALSE, or UNCERTAIN and choose FIX, DEFER, or IGNORE without changing code.
• Measurement planCreate 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).
• Reply to code reviewJudge current-head review findings, fix accepted defects, run verification, post evidence-backed replies, and request bounded re-review.
• Root cause analysisPerform an evidence-driven root cause analysis of an incident, recurring defect, failed release, or reliability problem.
• Spec reviewReview an engineering issue or specification against repository evidence for ambiguity, missing acceptance criteria, hidden scope, test gaps, and implementation risk.
• Ui polishPolish an existing UI screen with evidence.
• Ux testingUsability-test any web page or HTML prototype with AI agents acting as first-time users, then improve it in a measured loop.