agentleFS
javiarmestojaviarmesto/ALDC-AL-Development-Collection/skills/al-build/SKILL.md

al-build

Skill115 starsChanged 14 days agoMITView on GitHub

Build, package, and deploy AL extensions to Business Central environments.

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 8 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask and confirm with the user before proceeding.

    line 15
  2. Very specific:

    Build: Use al_build to compile the project

    line 21
  3. Very specific:

    Deploy: Use al_incremental_publish for rapid iteration (requires approval)

    line 23
  4. Distinctive:

    Verify: Check for any compilation errors

    line 24
  5. Very specific:

    Build: Use al_build with full validation

    line 27
  6. Very specific:

    Package: Create .app file with al_package

    line 28
  7. Very specific:

    Deploy: Use al_publish to deploy with debugging enabled (requires approval)

    line 30
  8. Distinctive:

    Test: Ensure all unit tests pass

    line 31
  9. Very specific:

    Build: Use al_build with strict validation

    line 34
  10. Very specific:

    Package: Create release package with al_package

    line 35
  11. Distinctive:

    Validation: Verify package integrity and dependencies

    line 36
  12. Distinctive:

    All production changes require explicit human authorization

    line 40
  13. Very specific:

    Use al_publish_existing_extension when deploying pre-built .app files

    line 43
  14. Distinctive:

    Verify package compatibility with target environment

    line 44
  15. Very specific:

    Use al_full_package when creating packages with all dependencies

    line 47
  16. Distinctive:

    Verify extension appears in Extension Management

    line 61
  17. Distinctive:

    Check all functionality works as expected

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build and Deploy AL Extension

Values in angle brackets come from the text typed after the command; ask for any that are missing.

Your goal is to build and deploy the AL extension for <DeploymentType> environment.

Select Deployment Strategy

Based on #codebase select the appropriate deployment strategy Ask and confirm with the user before proceeding.

Deployment Types

Based on the deployment type, use the appropriate strategy:

Development Environment

  1. Build: Use al_build to compile the project
  2. Review: Present build results for human approval
  3. Deploy: Use al_incremental_publish for rapid iteration (requires approval)
  4. Verify: Check for any compilation errors

Testing Environment

  1. Build: Use al_build with full validation
  2. Package: Create .app file with al_package
  3. Review: Present package details for human approval
  4. Deploy: Use al_publish to deploy with debugging enabled (requires approval)
  5. Test: Ensure all unit tests pass

Production Environment

  1. Build: Use al_build with strict validation
  2. Package: Create release package with al_package
  3. Validation: Verify package integrity and dependencies
  4. Documentation: Generate deployment checklist and present for review
  5. Human Gate: MANDATORY - Manual approval required before any production action
    • Note: Automated deployment to production is intentionally disabled as safeguard
    • All production changes require explicit human authorization

Existing Package Deployment

  • Use al_publish_existing_extension when deploying pre-built .app files
  • Verify package compatibility with target environment

Full Dependency Package

  • Use al_full_package when creating packages with all dependencies
  • Useful for offline installations or isolated environments

Error Handling

Monitor the output for:

  • Compilation errors
  • Dependency conflicts
  • Publishing failures
  • Permission issues

Post-Deployment Verification

After deployment:

  1. Verify extension appears in Extension Management
  2. Check all functionality works as expected
  3. Validate permissions are correctly applied
  4. Monitor for any runtime errors

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.