al-bc

Plugin al-bc from marketplace al-language-zed in Brad-Fullwood/al.language.zed. Commands read from the repo's manifest — 14 days ago.

Skills (8)

• bc-base-app-source

  Use whenever you need to read the AL source or body of a Business Central procedure, trigger or object - what a standard BC procedure does, how Microsoft implements something, show me the code for procedure P. Works for workspace code and for code that only exists inside a .app package such as Base

• bc-event-map

  Use for any Business Central event question - who subscribes to an event, who listens to an OnBefore or OnAfter event, which codeunit publishes it, what its parameters are, which integration event to subscribe to for a goal, why a subscriber does not fire. Covers the workspace and every .app package

• bc-impact-check

  Use for any question of the form who calls X, who uses X, what reads X, what depends on X, or what breaks if I rename, obsolete, delete or retype X. Covers Business Central fields, procedures, codeunits and tables, in the workspace and in .app packages, from the call graph rather than a text match.

• bc-object-id-allocator

  Use before creating any new Business Central object or adding a field, and whenever asked which object ID or field number is free. Picks the next free ID inside app.json's idRanges for a table, page, codeunit, report, query, xmlport, enum, interface, permission set or any extension kind, and the nex

• bc-symbol-lookup

  Use for any question about where an AL or Business Central object lives - where a table, field, page, codeunit, enum, interface or procedure is defined, which app or extension defines object N, what fields a table has, what values an enum accepts, what procedures a codeunit has. Answers from the al-

• bc-test-locally

  Use for any AL or Business Central test request - run the tests, write a test, find which tests cover a change or an object, check test coverage, or find out which tests need a live BC tenant. Most AL tests run locally on a built-in Rust interpreter with no BC server and no published app. Use it ins

• bc-upgrade-impact

  Use for any question about what a Business Central extension depends on, whether a dependency is missing or conflicting, or what moving to a new BC release or dependency version breaks. app.json's "application" and "platform" properties add implicit dependencies (Base Application, System Application

• bc-workspace-health

  Use before compiling or deploying a Business Central extension, and whenever asked to clean up, audit or review an AL app. Checks duplicate or out-of-range object IDs, SQL anti-patterns, dead code, missing ApplicationArea, DataClassification or tooltips, permission set coverage, complexity and dupli

Subagents (2)

• bc-cop-fixer

  Drive AL lint and workspace-check diagnostics to zero on a named set of files, one batch at a time. Use when an AL file or folder has analyzer warnings to clear, when asked to clean up cop or lint output, or before a build that must come back clean.

• bc-symbol-scout

  Use for any Business Central or AL lookup - where an object, table, field, codeunit or procedure is defined, what fields a table has, who calls or uses a symbol, who subscribes to an event, the source of a procedure including base-app code, what a change to a field breaks. Queries the AL symbol inde

MCP servers (1)

• al

  runs: ${CLAUDE_PLUGIN_ROOT}/scripts/al-bin.sh al-lsp mcp --project ${CLAUDE_PROJECT_DIR}

Hooks (2)

• SessionStart

  "${CLAUDE_PLUGIN_ROOT}"/scripts/al-session-context.sh

• SessionEnd

  "${CLAUDE_PLUGIN_ROOT}"/scripts/al-session-end.sh

Similar plugins