claude-configs

Run mutation testing against an AL project using al-mutate (MSDyn365BC.AL.Mutate). Identifies test gaps by applying AST-based mutations and checking whether the test suite catches them via al-runner. No BC instance required. Produces mutations.json and report.md.

Download AL symbol packages (.app files) for the current project's dependencies from Microsoft NuGet feeds. Reads app.json to determine required packages.

Look up Business Central base application source code (tables, pages, codeunits, events) from MSDyn365BC.Sandbox.Code.History. Use this to verify object structures, find event publishers, or check field definitions.

Quick reference for AL build pipeline. Auto-load when compilation, deployment, or testing is mentioned. For running commands, use /compile, /publish, or /run-tests.

Compile the AL project using al-compile. Runs analyzers, reports errors, and writes diagnostics to the task folder.

Implement AL/BC solution using parallel development agents and 4-specialist review team. Spawns N developer agents for parallel modules, then 4 reviewer agents for comprehensive code review.

Generate comprehensive technical documentation for implemented AL features using a docs-writer specialist agent.

Lightweight bug fix workflow. 3-tier classification for fast iteration without approval gates.

Initialize project context document for faster AL development workflows. One-time setup that reduces workflow runtime by 40-60%.

Deep requirements gathering through structured interview with specialist agent. Use when requirements are unclear, ambiguous, or complex.

Manage a local Business Central instance for development and testing. Detects host vs container environment automatically. Uses bc-linux run-tests.sh for test execution.

Design complete AL/BC solution using competitive solution design. Spawns 2-3 architect agents who debate approaches, then synthesizes winning plan.

Deploy the compiled AL app to a Business Central server using bc-publish. Requires .bcconfig.json configuration.

Quality review checklists for AL solution plans, code implementations, and test suites. Auto-load when reviewing agent output before presenting to user.

Execute AL test codeunits. Use al-runner for fast pure-logic tests (no BC required). Use bc-test for full integration tests against a running BC instance.

Develop comprehensive test suite using 4 parallel test engineer agents. Covers unit, integration, scenario, and edge case testing.

Adversarial test verification. Proves AL test suites are meaningful by mutation sweeps, assertion auditing, and coverage gap analysis. Always runs as a sub-agent with clean context — never inline.