Configuration

Accelerator supports project-specific configuration through markdown files with YAML frontmatter. Configuration allows you to provide project context, customise agent behaviour, and tune review settings. This page is the reference; for paste-able examples of common customisations, see the Configuration cookbook.

Config Files

File	Scope	Purpose
.accelerator/config.md	Team-shared (committed)	Shared project context and settings
.accelerator/config.local.md	Personal (gitignored)	Personal overrides and preferences

Local settings override team settings for the same key. Markdown bodies from both files are concatenated (team context first, then personal).

File Format

Both files use YAML frontmatter for structured settings and a markdown body for free-form project context:

---
agents:
  reviewer: my-custom-reviewer
review:
  disabled_lenses: [ portability, compatibility ]
  max_inline_comments: 15
  pr_request_changes_severity: major
---

## Project Context

  This is a Ruby on Rails application using PostgreSQL and Redis.

### Conventions
- Follow StandardRB for code style
- Use service objects for business logic
- All API endpoints require authentication

### Build & Test
- `bundle exec rspec` to run tests
- `bin/dev` to start the development server

The YAML frontmatter supports agents (override which agents skills spawn), review (customise review behaviour), paths (override where skills write output documents), templates (point to custom document templates), and work (customise work-item ID filename pattern and default project code). See /configure help for the full key reference.

Template Management

Templates control the structure of documents produced by skills (plans, ADRs, research, validation reports, PR descriptions). The configure skill provides subcommands for managing templates without manually locating plugin internals:

Command	Description
/configure templates list	List all templates with resolution source and path
/configure templates show <key>	Display the effective template content
/configure templates eject <key>	Copy plugin default to your templates directory
/configure templates eject --all	Eject all templates at once
/configure templates diff <key>	Show differences between your template and the default
/configure templates reset <key>	Remove your customisation, revert to plugin default

Available template keys: adr, codebase-research, design-gap, design-inventory, note, plan, plan-review, pr-description, pr-review, rca, validation, work-item, work-item-review.

A typical customisation workflow:

1. templates list to see what’s available and where each resolves from
2. templates eject plan to copy the plugin default to your templates directory
3. Edit the ejected file to match your project’s conventions
4. templates diff plan to review your changes against the default
5. templates reset plan if you want to revert to the plugin default

Templates are resolved in order: config path (templates.<key>) → templates directory (paths.templates, default .accelerator/templates/) → plugin default.

Managing Configuration

Run /configure to create or view your configuration. The skill walks you through gathering project context and writes the config file for you.

How It Works

• A SessionStart hook detects config files and injects a summary into the session context
• Skills read project context at invocation time via the ! preprocessor
• Config changes take effect on the next skill invocation (no session restart needed for skills); the SessionStart summary updates on session restart

Custom Review Lenses

You can add custom review lenses alongside the 13 built-in code review ones. Place them in .accelerator/lenses/ following the [name]-lens/SKILL.md convention. Custom lenses are auto-discovered and included in the lens catalogue. See the Review System for the built-in lens catalogue and /configure help for details and a minimal template.

Per-Skill Customisation

Beyond global context, you can provide context or instructions targeted at individual skills by placing files in .accelerator/skills/<skill-name>/:

.accelerator/skills/
  review-pr/
    context.md          # Context specific to PR review
    instructions.md     # Additional instructions for PR review
  create-plan/
    instructions.md     # Additional instructions for plan creation

• context.md — Injected after global project context. Use for information only one skill needs (e.g., review criteria for review-pr, architecture context for create-plan).
• instructions.md — Appended to the end of the skill’s prompt. Use to add steps, enforce conventions, or modify output format. Instructions at the end of the prompt typically take precedence when they conflict with earlier instructions.

Both files are optional. Directory names must match the skill name exactly (the part after /). The SessionStart hook warns about unrecognised directory names. See /configure help for the full reference.

Skill reference

For invocation and arguments, see the configure and init skill references.