auro
Commit, code-review, release-notes, pr, ado, and post-mortem skills for auro-formkit: guided Conventional Commits workflow, multi-model PR/local review, automated release-notes generation from Conventional Commits, PR creation with prompted base/draft, component labels, and post-mortem summaries and Discussion links, Azure DevOps work-item drafting, and post-mortem authoring with GitHub Discussions publishing.
Plugin auro from marketplace auro-ai in AlaskaAirlines/auro-ai. Commands read from the repo's manifest — 8 days ago.
What it installs
Skills (10)
adoDraft or edit an Azure DevOps work item for the Auro design system. Run when asked to create, write, or file a new ADO ticket (bug or user story), or to edit or refine an existing one. Requires a mode argument — `new` to create a work item, or an ADO ticket number to edit an existing one. In create
close-dependabotBulk-close open Dependabot pull requests across every Auro repository. Run when asked to close or clean up the open Dependabot PRs across the Auro repos. Resolves the Auro repo set from the AlaskaAirlines `auro-team` GitHub team (non-archived repos), finds every open PR authored by Dependabot in tho
code-reviewReview a GitHub pull request or local branch for bugs and correctness issues. Use a PR number to review a PR — findings are previewed in chat and saved, and only posted to GitHub when you re-run with `post` — or `local` (or no argument) to review the current branch in chat. An optional effort level
commitGuided commit workflow for auro-formkit — takes an ADO ticket or PR number as its argument (or `skip` to commit without one, or `amend` to fold staged changes into the previous commit), checks you are not on dev/main/master, verifies the branch is synced, then builds a Conventional Commits message f
create-rcsBuild a Release Candidate Summary (RCS) from the Auro Design System Azure DevOps board for a chosen sprint iteration. Run when asked to create an RCS, or the Release tickets for a sprint or an npm package. Not for sprint reports, release notes, or cutting or publishing a release. It prompts for whic
doc-reviewReview the component documentation on the current branch against the Auro "Content guidelines for component documentation" (WC-Generator discussion #660). Run when asked to review, check, or fix component documentation against the Auro content guidelines, or when another skill needs those checks run
post-mortemAuthor or refresh a post-mortem for a piece of work, keyed to an Azure DevOps ticket. Run when asked to write, create, or update a post-mortem for the current branch's work. Prompts for the ADO ticket number (offering to reuse the ticket from the most recent post-mortem), then gathers context from t
prOpen a GitHub pull request for the current branch — assigned to you, seeded from the repo's .github PR template. Run when asked to open or create a pull request for the current branch, or to refresh an existing PR's ticket summary. Prompts whether to target the repo's default branch or a branch you
release-notesGenerate or update the next release-notes document for auro-formkit. Run when asked to write, generate, or update the release notes for the next auro-formkit release. Determines the next semantic version from the Conventional Commits since the last released version (BREAKING CHANGE → major, feat → m
sprint-reportGenerate a sprint report from the Auro Design System Azure DevOps board. Run when asked for a sprint report, sprint summary, or sprint metrics for the Auro board — it is long-running (many ADO and git calls). Not for a quick question about one ticket, creating or editing work items, or Release ticke
Subagents (12)
code-reviewer-opus-highInternal to /auro:code-review — do not invoke directly. Reviews a diff (Opus, high effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-opus-lowInternal to /auro:code-review — do not invoke directly. Reviews a diff (Opus, low effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-opus-maxInternal to /auro:code-review — do not invoke directly. Reviews a diff (Opus, max effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-opus-mediumInternal to /auro:code-review — do not invoke directly. Reviews a diff (Opus, medium effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-opus-xhighInternal to /auro:code-review — do not invoke directly. Reviews a diff (Opus, xhigh effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-sonnet-highInternal to /auro:code-review — do not invoke directly. Reviews a diff (Sonnet, high effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-sonnet-lowInternal to /auro:code-review — do not invoke directly. Reviews a diff (Sonnet, low effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-sonnet-maxInternal to /auro:code-review — do not invoke directly. Reviews a diff (Sonnet, max effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-sonnet-mediumInternal to /auro:code-review — do not invoke directly. Reviews a diff (Sonnet, medium effort) and returns findings as JSON; never edits files or posts comments.
code-reviewer-sonnet-xhighInternal to /auro:code-review — do not invoke directly. Reviews a diff (Sonnet, xhigh effort) and returns findings as JSON; never edits files or posts comments.
doc-review-componentInternal to /auro:doc-review — do not invoke directly. Reviews one work unit (one component, or part of one) of a `/auro:doc-review all` run in a monorepo against the Auro content guidelines, applies the fixes in write mode, and returns the results as JSON; never runs builds, commits, or posts comme
doc-reviewerInternal to /auro:code-review — do not invoke directly. Runs the doc-review checks (Auro content guidelines + claim verification) on a diff in review mode and returns findings as JSON; never edits repository files or posts comments.
Maintain auro?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.