business-central-al

Plugin business-central-al from marketplace verosoft-design in Verosoft-Design/claude-plugins. Commands read from the repo's manifest — 6 days ago.

Skills (92)

• al-docs

  This skill should be used when the user asks to "document AL code", "generate docs for this app", "create documentation for this extension", "document this BC app", "set up docs for this AL project", "refresh my docs after code changes", "what documentation is missing", or wants to bootstrap, update

• al-add-bcpt-app

  Add a new AL performance test app (Business Central Performance Toolkit) to an existing AL-Go repository via the Create a new performance test app workflow. Use when the user wants BCPT-based performance regression testing in CI.

• al-add-test-app

  Add a new AL test app to an existing AL-Go repository via the Create a new test app workflow. Use when the user wants to introduce automated tests to a BC app that does not yet have a test project.

• al-agents-review

  Review AL code that implements or invokes Business Central Agent SDK surfaces using BCQuality's community agents knowledge, covering agent interfaces, setup and creation, tasks, capability registration, profiles, access controls, instructions, and session-bound subscribers.

• al-apply-rulesets

  Drop Microsoft's official BCApps analyzer rulesets into the current AL workspace and wire AL-Go and VS Code to point at them. Use to align a project with Microsoft's own quality bar — every analyzer rule is an Error unless explicitly silenced for a documented reason.

• al-apply-vscode-defaults

  Apply Microsoft's BCApps VS Code defaults to the current AL workspace by merging into .vscode/settings.json. Enables CodeCop / AppSourceCop / PerTenantExtensionCop / UICop, semantic highlighting, formatOnSave, and the BCApps defaults that Microsoft uses internally.

• al-appsource-review

  Review an AL app for AppSource readiness using BCQuality's AppSource knowledge, covering app.json metadata, permission sets, profiles, setup and usage entry points, UsageCategory, GuiAllowed for dialogs, and help metadata.

• al-base-app-source

  Get Microsoft's Business Central base application source (Base Application, System Application, country layers) onto disk at the project's version so field names, procedures, event publishers and posting logic can be read and grepped instead of guessed. Use before subscribing to a base-app event, ex

• al-breaking-changes-review

  Review AL changes for breaking changes using BCQuality's breaking-changes knowledge, covering public procedure and event signatures, access modifiers, published fields, and the Obsolete lifecycle (ObsoleteState, ObsoleteTag, CLEAN preprocessor symbols).

• al-build-and-publish

  Orchestrates the AL inner-development loop using the altool launchmcpserver MCP. Use when the user asks to build, compile, validate, publish, deploy, or roll an AL extension out to a sandbox or production environment, or asks the agent to download symbols, check diagnostics, or chain any of these st

• al-build

  Build the AL project and produce a .app package via the AL MCP. Use when the goal is a deployable artifact — before publishing, before delivering to a release artifact store, or to validate that the full pipeline (including .app generation) succeeds.

• al-call-graph

  Build and query a static call graph of the project's AL apps (and optionally base-app source) with ALTool's `al graph` commands, to answer "who calls this procedure", "what can reach this internal code", "what does this change affect", including event and interface edges. Use before changing a proce

• al-code-review

  Run a comprehensive BCQuality-driven review of AL code by composing the 19 leaf review skills (performance, security, privacy, upgrade, style, UI, error handling, events, interfaces, breaking changes, web services, testing, data modeling, query, reporting, AppSource, telemetry, SCM, finance), then a

• al-compile

  Validate AL code without producing a .app package via the AL MCP. Faster than al-build. Use when the goal is to surface compile errors and analyzer findings quickly (PR gate, save-time check, before iterating on a fix).

• al-conventions

  Business Central AL coding conventions (naming, files, labels, Locked, XML docs, license header, tests) with the full reference docs. Loads automatically when working on .al files and app.json.

• al-create-online-dev-env

  Provision a Business Central online dev sandbox via the Create Online Dev. Environment workflow and update launch.json to target it. Use when the user wants a fresh BC environment for development against a specific app version, without needing local Docker.

• al-current

  Re-run the AL-Go build against the current BC version artifact via the Test Current workflow. Use to verify the app still builds and passes tests against the currently shipped BC version, independent of the default artifact pinned in settings.

• al-data-modeling-review

  Review AL tables and data design using BCQuality's data-modeling knowledge, covering setup and master tables, keys, No. Series, TableRelation, Blocked and audit fields, table triggers, table extensions, and document and posting patterns.

• al-deploy-docs

  Build and publish the aldoc reference documentation site to GitHub Pages via the Deploy Reference Documentation workflow. Use to generate and ship a static documentation site for the project's AL objects, procedures, and integration events.

• al-docs

  Generate, refresh, or audit hierarchical documentation for a Business Central AL codebase. Wraps the BCApps al-docs-plugin (init / update / audit modes) to produce or maintain data-model, business-logic, extensibility, and patterns docs adapted to AL object types, table relationships, event-driven a

• al-entry

  Route a Business Central AL task to the right BCQuality action skill. Builds the Entry task context, refreshes the knowledge index, applies BCQuality's entry-point routing (relevance, goal match, super-skill precedence, layer precedence), and executes the dispatched skill or skills. Use as the front

• al-error-handling-review

  Review AL code for error-handling issues using BCQuality's error-handling knowledge, covering Error and ErrorInfo usage, actionable and collectible errors, TryFunction and GetLastErrorText, Confirm in validation, and trigger return values.

• al-events-review

  Review AL event publishers and subscribers using BCQuality's events knowledge, covering IntegrationEvent and BusinessEvent design, IsHandled patterns, subscriber binding and parameters, database trigger events, and ChangeCompany behavior.

• al-feedback-loops

  How to build, test, reproduce, inspect data and check the UI in Business Central AL, ranked by speed. Use whenever a process skill (superpowers test-driven-development, systematic-debugging, verification-before-completion; mattpocock tdd, diagnosing-bugs) asks for a build command, a test run, a red-

• al-finance-review

  Review AL code that touches financial posting using BCQuality's Finance knowledge, covering general journal posting, ledger corrections, applications, VAT handling, and posting-linked dimensions.

• al-go-lifecycle

  Orchestrates the AL-Go for GitHub lifecycle for Business Central AL projects via gh workflow run. Use when the user asks to scaffold a new app, add a test app, deploy to a sandbox or production environment, create a release, publish to AppSource, update AL-Go system files, increment version numbers,

• al-go-live

  Compound lifecycle command that takes a feature from local build to AppSource release. Walks through al-build → al-publish-sandbox → smoke tests → al-release → al-publish-appsource. Use when the user wants the full end-to-end "ship it" flow with explicit confirmation gates at each destructive step.

• al-import-existing-app

  Import an existing AL app (.app or .zip) into an AL-Go repository via the Add existing app or test app workflow. Use when migrating a legacy non-AL-Go project into the AL-Go lifecycle, or when a customer hands over a precompiled .app to onboard.

• al-increment-version

  Bump version numbers in one or more AL-Go projects via the Increment Version Number workflow. Use to roll the repo version after a release, to coordinate a major bump across projects, or to set an explicit version string.

• al-init-keyvault

  Wire Azure Key Vault into an AL-Go repository so secrets live in KV instead of GitHub Secrets, plus optionally configure Azure-Trusted-Signing for .app codesign. Use when the user wants centralized secret rotation, fewer per-repo GitHub Secrets, or KV-based codesigning.

• al-init

  Write a CLAUDE.md for a Business Central AL repository that records its real conventions (apps, ID ranges, affix, file naming, folder layout, namespaces, test setup, build and test commands, BC server), detected from the code, so every session starts with them.

• al-interfaces-review

  Review AL interfaces and extensible enums with implementations using BCQuality's interfaces knowledge, covering implements, DefaultImplementation, UnknownValueImplementation, and replacing case-over-enum strategy selection.

• al-new-appsource

  Scaffold a new AL-Go for GitHub repository for an AppSource app, then create the first app inside it via the Create a new app workflow. Use when the user wants a brand-new BC AppSource project ready for CI/CD plus eventual AppSource delivery.

• al-new-pte

  Scaffold a new AL-Go for GitHub repository for a Per Tenant Extension (PTE), then create the first app inside it via the Create a new app workflow. Use when the user wants a brand-new BC PTE project ready for CI/CD.

• al-next-major

  Re-run the AL-Go build against the next major BC version artifact via the Test Next Major workflow. Use to surface upcoming-major-release compatibility breaks early, typically months ahead of the actual release.

• al-next-minor

  Re-run the AL-Go build against the next minor BC version artifact via the Test Next Minor workflow. Use to surface upcoming-release compatibility breaks before BC publishes the new minor version.

• al-performance-review

  Review AL code for performance issues using BCQuality's performance knowledge, covering filtering before iterating, SetLoadFields, IsEmpty vs Count, FindSet and locking, CalcFields/CalcSums, per-row work and Commit inside loops, keys and SIFT, and caching.

• al-privacy-review

  Review AL code for privacy issues using BCQuality's privacy knowledge, covering DataClassification on tables and fields, personal data in telemetry and error text, and retention policies.

• al-profile

  Find out why something is slow in Business Central with Microsoft's Performance Profiling MCP server (ALTool launchprofilingmcpproxy). Schedules profiling for a session, collect the CPU profiles with SQL/HTTP timings and memory estimate, and explain the hot AL paths against BCQuality performance kno

• al-publish-appsource

  Submit a release to Microsoft AppSource via the Publish To AppSource workflow. Optionally promote the submission past Preview to public AppSource (Go Live). Use only on AL-Go-AppSource-typed repos where Partner Center has already been seeded with the product.

• al-publish-sandbox

  Publish a built .app to a Business Central sandbox environment via the AL MCP. Handles Entra ID sign-in if needed and supports cloud (sandbox/production) and on-prem targets. Use after a successful al-build, or directly with an existing .app via skipBuild.

• al-publish-to-environment

  Deploy a specific build's artifacts to one or more BC environments via the Publish To Environment workflow. Use for production manual deploys (since (PROD)/(FAT) environments are excluded from CD), for promoting a PR build to a sandbox, or for re-deploying an older release.

• al-query-review

  Review AL query objects and Query variable usage using BCQuality's query knowledge, covering filter order relative to Open, DataItemTableFilter and ColumnFilter precedence, and reopening or reusing query instances.

• al-release

  Cut a GitHub release via the Create release workflow. Tags HEAD, builds release notes from commits, publishes the release with .app artifacts and source, and opens an Increment Version Number PR for the next dev cycle. Use when a build is ready to become an officially-named release.

• al-reporting-review

  Review AL reports and report extensions using BCQuality's reporting knowledge, covering data items and their triggers, CurrReport.Skip/Break/Quit, request pages, running and saving reports, and layouts.

• al-run-tests

  In AL Builder, compile locally and publish/run tests through the bc_* broker tools. Otherwise publish to the configured Business Central server and run AL test codeunits with `al runtests`, returning pass/fail per test method as structured JSON. Use for the red and green steps of TDD, to reproduce a

• al-scaffold-module

  Scaffold a new AL feature module following BCApps conventions (facade Codeunit + Internal Impl, four-tier permission sets, namespace, license header, XML docs) OR the consuming repo's existing per-object-type folder convention (e.g. TAG-style BC/{API,CodeUnit,Enums,...}). Use when adding a brand-new

• al-scm-review

  Review AL code that touches supply chain workflows using BCQuality's SCM knowledge, covering inventory costing, item application, reservations, order and item tracking, warehouse handling, transfers, and planning.

• al-secrets-setup

  Interactive wizard for minting the JSON-shaped secrets that AL-Go workflows need (AuthContext, AppSourceContext, GhTokenWorkflow, AdminCenterApiCredentials, StorageContext, NuGetContext, GitHubPackagesContext). Use when an AL-Go workflow fails on missing or expired secrets, or when first wiring up C

• al-security-review

  Review AL code for security issues using BCQuality's security knowledge, covering SecretText and credential handling, NonDebuggable, IsolatedStorage, permission sets and inherent or indirect permissions, IntegrationEvent bypass parameters, HTTP and URI validation, and RecordRef access.

• al-setup

  Diagnose and (with explicit user permission) install the AL MCP prerequisites. Use when the session-start context reports AL MCP is missing, when an AL MCP tool call fails because altool/al is not on PATH, or before any /al-* command is used for the first time on a fresh machine.

• al-snapshot-debug

  Capture what actually happened in a failing Business Central session with Microsoft's Snapshot Debugging MCP server (ALTool launchsnapshotmcpproxy). Arms a snapshot, the user reproduces the problem, and the recording (AL errors with call stack and variables at snappoints) comes back for diagnosis. U

• al-style-review

  Review AL code against BCQuality's style knowledge, covering naming, labels and localization, captions and tooltips, API page naming, object and file organization, and code conventions. Rules already enforced by the compiler or CodeCop are left to those analyzers.

• al-symbol-search

  Search AL symbols (objects, fields, methods, keys, actions, triggers) across the project and its dependencies via the AL MCP, or across everything installed on the connected environment. Use when the agent needs to locate a codeunit, table, page, enum, interface, or member by name, namespace, or doc

• al-symbols

  Download dependent AL symbol packages into the project's .alpackages folder via the AL MCP. Use when symbols are missing, after editing app.json dependencies, or to refresh symbols from a connected BC environment.

• al-telemetry-review

  Review AL telemetry code using BCQuality's telemetry knowledge, covering Session.LogMessage and Feature Telemetry, verbosity, TelemetryScope, custom dimensions, and data classification of telemetry signals.

• al-testing-review

  Review AL test code using BCQuality's testing knowledge, covering test codeunits and runners, TestIsolation and TransactionModel, TestPermissions, UI handlers and HandlerFunctions, asserterror and expected errors, and fixtures.

• al-troubleshoot

  Dispatch the AL-Go Troubleshooting workflow to dump repo settings and the names of available secrets. Use as the first diagnostic step when any AL-Go workflow misbehaves, when secrets seem missing, or when the user is unsure what's configured.

• al-ui-review

  Review AL pages, page extensions, control add-ins, and notification code using BCQuality's UI knowledge, covering captions, tooltips, UI text, notifications, page-type conventions, and accessibility.

• al-ui-test

  Check Business Central changes through the real web client. Replay page scripting recordings headlessly with Microsoft's bc-replay (Playwright), write new recordings for a page/action change, or explore the live UI with the Playwright MCP. Use after changing pages, page extensions, actions, field vi

• al-update-system-files

  Dispatch the Update AL-Go System Files workflow to refresh AL-Go scripts and workflows from the template repo. Use when the user wants to pick up new AL-Go features, fixes, or to silence the "newer system files available" warning in CI/CD output.

• al-upgrade-review

  Review AL upgrade and install code using BCQuality's upgrade knowledge, covering upgrade codeunits, upgrade tags, data migration and transfer patterns, and what upgrade code must not do (for example ChangeCompany).

• al-web-services-review

  Review AL API surfaces and integrations using BCQuality's web-services knowledge, covering API pages and queries, OData naming and keys, bound actions, outbound HttpClient calls, and webhook handling.

• al-write-test

  Generate a Business Central AL test using the ALTest domain-agent prompt from microsoft/BC-Bench, the only custom agent BC-Bench has measured on test generation (62.4% vs 51.7% mean, pass^5 39.6% vs 22.8%, Claude Opus 4.6 on GitHub Copilot CLI, April-May 2026). Use when the user asks to write, scaff

• bc-server-setup

  Set up a Business Central server this project can publish to, run tests on and drive through the web client, and record it in .claude/bc-server.json. Choices are a local Docker container via BcContainerHelper (Windows), an online sandbox, or an existing on-prem/dev server, including the team's BC Do

• bcq-review-agents

  Run only the BCQuality Agents (Agent SDK) review (al-agents-review) on AL code, covering agent interfaces, setup and creation, tasks, capability registration, profiles, access controls, instructions, and session-bound subscribers. It is not part of `/bcq-review`. Use when the user specifically wants

• bcq-review-appsource

  Run only the BCQuality AppSource review (al-appsource-review) on AL code, covering app.json metadata, permission sets, profiles, setup and usage entry points, UsageCategory, GuiAllowed for dialogs, and help metadata. The other 18 leaves and the `al-code-review` self-review pass are skipped. Use when

• bcq-review-breaking-changes

  Run only the BCQuality Breaking changes review (al-breaking-changes-review) on AL code, covering public procedure and event signatures, access modifiers, published fields, and the Obsolete lifecycle (ObsoleteState, ObsoleteTag, CLEAN preprocessor symbols). The other 18 leaves and the `al-code-review

• bcq-review-data-modeling

  Run only the BCQuality Data modeling review (al-data-modeling-review) on AL code, covering setup and master tables, keys, No. The other 18 leaves and the `al-code-review` self-review pass are skipped. Use when the user specifically wants data modeling feedback on a diff, a file, or an app folder.

• bcq-review-error-handling

  Run only the BCQuality Error handling review (al-error-handling-review) on AL code, covering Error and ErrorInfo usage, actionable and collectible errors, TryFunction and GetLastErrorText, Confirm in validation, and trigger return values. The other 18 leaves and the `al-code-review` self-review pass

• bcq-review-events

  Run only the BCQuality Events review (al-events-review) on AL code, covering IntegrationEvent and BusinessEvent design, IsHandled patterns, subscriber binding and parameters, database trigger events, and ChangeCompany behavior. The other 18 leaves and the `al-code-review` self-review pass are skippe

• bcq-review-finance

  Run only the BCQuality Finance review (al-finance-review) on AL code, covering general journal posting, ledger corrections, applications, VAT handling, and posting-linked dimensions. The other 18 leaves and the `al-code-review` self-review pass are skipped. Use when the user specifically wants finan

• bcq-review-interfaces

  Run only the BCQuality Interfaces review (al-interfaces-review) on AL code, covering implements, DefaultImplementation, UnknownValueImplementation, and replacing case-over-enum strategy selection. The other 18 leaves and the `al-code-review` self-review pass are skipped. Use when the user specifical

• bcq-review-performance

  Run only the BCQuality Performance review (al-performance-review) on AL code, covering filtering before iterating, SetLoadFields, IsEmpty vs Count, FindSet and locking, CalcFields/CalcSums, per-row work and Commit inside loops, keys and SIFT, and caching. The other 18 leaves and the `al-code-review`

• bcq-review-privacy

  Run only the BCQuality Privacy review (al-privacy-review) on AL code, covering DataClassification on tables and fields, personal data in telemetry and error text, and retention policies. The other 18 leaves and the `al-code-review` self-review pass are skipped. Use when the user specifically wants p

• bcq-review-query

  Run only the BCQuality Query review (al-query-review) on AL code, covering filter order relative to Open, DataItemTableFilter and ColumnFilter precedence, and reopening or reusing query instances. The other 18 leaves and the `al-code-review` self-review pass are skipped. Use when the user specifical

• bcq-review-reporting

  Run only the BCQuality Reporting review (al-reporting-review) on AL code, covering data items and their triggers, CurrReport.Skip/Break/Quit, request pages, running and saving reports, and layouts. The other 18 leaves and the `al-code-review` self-review pass are skipped. Use when the user specifica

• bcq-review-scm

  Run only the BCQuality Supply Chain Management review (al-scm-review) on AL code, covering inventory costing, item application, reservations, order and item tracking, warehouse handling, transfers, and planning. The other 18 leaves and the `al-code-review` self-review pass are skipped. Use when the

• bcq-review-security

  Run only the BCQuality Security review (al-security-review) on AL code, covering SecretText and credential handling, NonDebuggable, IsolatedStorage, permission sets and inherent or indirect permissions, IntegrationEvent bypass parameters, HTTP and URI validation, and RecordRef access. The other 18 l

• bcq-review-style
• bcq-review-telemetry
• bcq-review-testing
• bcq-review-ui
• bcq-review-upgrade
• bcq-review-web-services
• bcq-review
• bcq-update
• bcq-write-knowledge
• business-central-al-tdd
• scaffold-handler-methods
• scaffold-test-codeunit
• tdd-checklist

Subagents (1)

• bc-explorer

  Finds facts in Business Central base-app source and symbols without filling the main context. Use to answer "which event fires when...", "what is the exact signature of...", "which field/procedure/enum value...", "how does the base app post/validate..." before writing AL that depends on it. Returns

MCP servers (1)

• al

  runs: altool launchmcpserver --transport stdio ${CLAUDE_PROJECT_DIR}

Hooks (2)

• SessionStart

  python3

• PostToolUse

  python3

Language servers (1)

• al

Similar plugins