accelerator

browser-executor

Resolves the absolute path of the Playwright executor (run.sh) for browser agents. Preloaded by agent definitions that need to invoke the executor without self-discovery; not intended for direct user invocation.

Data & Documents Listed

configure

View, create, or edit Accelerator plugin configuration. Manage document templates.

init

Prepare a repository with the directories and gitignore entries that Accelerator skills expect. Safe to run repeatedly.

migrate

Apply pending Accelerator meta-directory migrations to bring a repo into line with the latest plugin schema. Destructive by default but guarded — refuses to run on a dirty working tree and prints a one-line preview per pending migration before applying.

paths

Resolves all configured document-discovery paths for the current project. Preloaded by agent definitions that need config-driven directory locations; not intended for direct user invocation.

create-adr

Interactively create an architecture decision record (ADR). Use when the user wants to document an architectural decision, technology choice, or significant design decision. Guides through context gathering, options analysis, and consequence documentation.

Data & Documents Listed

extract-adrs

Extract architecture decision records from existing meta documents (research, plans). Scans documents for implicit or explicit architectural decisions and converts selected ones into formal ADRs. Use when decisions are buried in research or planning documents and need to be captured formally.

review-adr

Review an architecture decision record for quality and completeness, then accept, reject, or suggest revisions. Enforces ADR immutability — only proposed ADRs can be modified, accepted ADRs can only transition to superseded or deprecated. Use when a proposed ADR is ready for review, or when an accepted ADR needs to be deprecated.

analyse-design-gaps

Compare two design inventories produced by inventory-design and emit a structured gap artifact whose prose paragraphs satisfy the extract-work-items cue-phrase contract. Use after running inventory-design for both a current and target design surface. The resulting gap artifact under meta/design-gaps/ feeds directly into /accelerator:extract-work-items to produce actionable work items.

describe-pr

Generate a comprehensive pull request description following the repository's standard template. Use when the user wants to create or update a PR description.

respond-to-pr

Respond to pull request review feedback interactively, working through each item with verification and code changes. Use when the user wants to address PR review comments.

review-pr

Review a pull request through multiple quality lenses and present a compiled analysis with inline comments. Use when the user wants a thorough PR review.

Show all 57 bundled skills

attach-jira-issue

Use this skill only when the user explicitly invokes /attach-jira-issue to upload one or more local files as attachments to a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Shows a preview of what will be uploaded and requires explicit confirmation before POSTing.

comment-jira-issue

Use this skill only when the user explicitly invokes /comment-jira-issue to add, list, edit, or delete comments on a Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Subcommands: add (post a new comment), list (fetch all comments with pagination), edit (update an existing comment), delete (remove a comment — irreversible). Write subcommands show a payload preview and require explicit confirmation before calling the API.

create-jira-issue

Use this skill only when the user explicitly invokes /create-jira-issue to create a new Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts a project key, issue type, summary, optional Markdown body, and optional fields (assignee, priority, labels, components, parent, custom fields). Converts the body to ADF, shows a payload preview, requires explicit confirmation, then POSTs to Jira and returns the new issue key.

init-jira

Set up the Jira Cloud integration for this project. Verifies credentials against a real Jira Cloud tenant, discovers the tenant's custom-field catalogue and project list, and persists the results under `<paths.integrations>/jira/` (default `.accelerator/state/integrations/jira/`) as team-shared, version-controlled JSON caches. Idempotent: safe to re-run after credential or project changes.

Data & Documents Solid

search-jira-issues

Use this skill whenever the user wants to search, list, or filter Jira tickets — by assignee, status, label, project, type, component, reporter, parent, or free text — even if they say 'find', 'show me', 'what's open', 'list my tickets', or similar phrasing rather than 'search Jira'. Composes safe JQL from structured flags, executes a paginated search against a Jira Cloud tenant, and renders a summary table of the results. Supports --render-adf to convert ADF descriptions to Markdown inline. Prefer this skill over raw JQL whenever the user's intent maps to a structured flag.

show-jira-issue

Use this skill when the user asks about a specific Jira issue by key (e.g. PROJ-123, ENG-456) — for viewing the description, status, comments, transitions, or any other field. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' a key, or asks any direct question about an issue they reference. Do NOT trigger when an issue key appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.

transition-jira-issue

Use this skill only when the user explicitly invokes /transition-jira-issue to move a Jira issue through its workflow by state name. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts an issue key and target state name (case-insensitive). Shows a transition preview and requires explicit confirmation before posting.

update-jira-issue

Use this skill only when the user explicitly invokes /update-jira-issue to modify an existing Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts an issue key and at least one mutating flag (summary, body, priority, assignee, labels, components, parent, custom fields). Shows a payload preview with explicit set-vs-update label semantics, requires explicit confirmation, then PUTs to Jira.

attach-linear-issue

Use this skill only when the user explicitly invokes /attach-linear-issue to attach a link or a binary file to an existing Linear issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Link mode registers an external URL; binary mode uploads a local file via Linear's pre-signed URL flow and registers the resulting asset. Shows a preview, requires explicit confirmation, then attaches.

comment-linear-issue

Use this skill only when the user explicitly invokes /comment-linear-issue to add a Markdown comment to an existing Linear issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows the comment preview, requires explicit confirmation, then posts the comment.

create-linear-issue

Use this skill only when the user explicitly invokes /create-linear-issue to create a new Linear issue from a local work-item file. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It reads the work item's title and Markdown body, shows a payload preview, requires explicit confirmation, then creates the issue and writes the remote-allocated identifier (e.g. BLA-123) back into the file's external_id frontmatter field.

init-linear

Set up the Linear integration for this project. Verifies a Linear personal API key against the real Linear GraphQL API, lets you pick one team, and persists that team plus its WorkflowState catalogue under `<paths.integrations>/linear/` (default `.accelerator/state/integrations/linear/`). `catalogue.json` is team-shared and version-controlled; `viewer.json` is per-developer and gitignored. Idempotent: safe to re-run after credential or team changes.

search-linear-issues

Use this skill whenever the user wants to search, list, or filter Linear issues — by state, assignee, label, or free text — even if they say 'find', 'show me', 'what's open', 'list my issues', or similar phrasing rather than 'search Linear'. Composes a Linear IssueFilter from structured flags, executes a cursor-paginated search scoped to the configured team, and renders a summary table of the results. Prefer this skill over raw GraphQL whenever the user's intent maps to a structured flag.

show-linear-issue

Use this skill when the user asks about a specific Linear issue by identifier (e.g. BLA-123, ENG-456) — for viewing the description, state, assignee, or comments. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' an identifier, or asks any direct question about an issue they reference. Do NOT trigger when an identifier appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.

transition-linear-issue

Use this skill only when the user explicitly invokes /transition-linear-issue to move an existing Linear issue to a different workflow state. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. The target state name is resolved to its UUID from the cached catalogue (no live lookup). Shows a preview, requires explicit confirmation, then applies the transition.

update-linear-issue

Use this skill only when the user explicitly invokes /update-linear-issue to change fields on an existing Linear issue (title, description, state, assignee, priority). This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows a payload preview, requires explicit confirmation, then applies the update.

create-note

Interactively capture a short-form note. Use when jotting down an observation, insight, or strategy snippet as a short-form note in meta/notes/ — e.g. "make a note of this", "jot this down", "capture a note".

create-plan

Create detailed implementation plans through interactive, iterative collaboration. Use when the user needs to plan a feature, refactoring, or task.

implement-plan

Execute an approved implementation plan from the configured plans directory. Use when the user wants to implement a plan phase by phase with verification.

review-plan

Review an implementation plan through multiple quality lenses and collaboratively iterate based on findings. Use when the user wants to evaluate a plan before implementation.

Testing & QA Listed

stress-test-plan

Interactively stress-test an implementation plan by grilling the user on decisions, edge cases, and assumptions to find issues, inconsistencies, and gaps before implementation begins.

validate-plan

Validate that an implementation plan was correctly executed by verifying success criteria and identifying deviations. Use after implementing a plan to verify correctness.

research-codebase

Conduct comprehensive codebase research by spawning parallel sub-agents and synthesising findings into a research document. Use when the user needs to deeply understand a codebase area or answer technical questions.

research-issue

Investigate production issues and bugs through hypothesis-driven debugging. Accepts stacktraces, logs, error messages, or vague behavioral descriptions and produces a root cause analysis.

architecture-lens

Architecture review lens for evaluating structural integrity, coupling, cohesion, and evolutionary fitness. Used by review orchestrators — not invoked directly.

clarity

Work-item review lens for evaluating unambiguous communication — referent clarity, internal consistency, jargon handling, and actor/outcome identification. Used by review orchestrators — not invoked directly.

code-quality-lens

Code quality review lens for evaluating design principles, error handling, complexity, testability, and maintainability. Used by review orchestrators — not invoked directly.

compatibility-lens

Compatibility review lens for evaluating API contract stability, cross-platform support, protocol compliance, and dependency management. Used by review orchestrators — not invoked directly.

completeness

Work-item review lens for evaluating structural and informational completeness — section presence, content density, kind-appropriate content, and frontmatter integrity. Used by review orchestrators — not invoked directly.

correctness-lens

Correctness review lens for evaluating logical validity, boundary conditions, invariant preservation, concurrency correctness, and state management. Used by review orchestrators — not invoked directly.

API & Backend Listed

database-lens

Database review lens for evaluating migration safety, schema design, query correctness, and data integrity. Used by review orchestrators — not invoked directly.

dependency

Work-item review lens for evaluating explicit capture of blockers, consumers, external systems, and ordering. Used by review orchestrators — not invoked directly.

Data & Documents Listed

documentation-lens

Documentation review lens for evaluating documentation completeness, accuracy, and audience-appropriateness. Used by review orchestrators — not invoked directly.

API & Backend Listed

performance-lens

Performance review lens for evaluating algorithmic efficiency, resource usage, and concurrency efficiency. Used by review orchestrators — not invoked directly.

portability-lens

Portability review lens for evaluating environment independence, deployment flexibility, and vendor lock-in avoidance. Used by review orchestrators — not invoked directly.

safety-lens

Safety review lens for evaluating data loss prevention, operational safety, and protective mechanisms against accidental harm. Used by review orchestrators — not invoked directly.

scope

Work-item review lens for evaluating sizing, decomposition, and orthogonality of requirements. Used by review orchestrators — not invoked directly.

security-lens

Security review lens for evaluating threats, vulnerabilities, and missing protections. Used by review orchestrators — not invoked directly.

standards-lens

Standards compliance review lens for evaluating project conventions, API standards, and accessibility. Used by review orchestrators — not invoked directly.

Testing & QA Listed

test-coverage-lens

Test coverage review lens for evaluating testing strategy adequacy, test quality, and test architecture. Used by review orchestrators — not invoked directly.

Testing & QA Listed

testability

Work-item review lens for evaluating whether Acceptance Criteria and requirements admit a concrete verification strategy — each criterion must be specific, measurable, and verifiable. Used by review orchestrators — not invoked directly.

usability-lens

Usability review lens for evaluating developer experience, API ergonomics, configuration complexity, and onboarding. Used by review orchestrators — not invoked directly.

plan-review-output-format

Output format specification for plan review agents. Defines the JSON schema, field reference, severity emoji prefixes, and finding body format for plan reviews.

pr-review-output-format

Output format specification for PR review agents. Defines the JSON schema, field reference, severity emoji prefixes, and comment body format for PR reviews.

work-item-review-output-format

Output format specification for work-item review agents. Defines the JSON schema, field reference, severity emoji prefixes, and finding body format for work-item reviews. Used by review orchestrators — not invoked directly.