菜单
Prepare BC-Bench release notes for review. Use when creating a release, screening merged PRs since the previous version tag for changes that may affect evaluation results, matching recent GitHub release notes, or reporting the agent harness and development tool versions shipped by a release.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/microsoft/BC-Bench --skill create-release命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Guide a Business Central user through preparing a high-quality extensibility request and filing it as a GitHub issue in microsoft/ALAppExtensions. The skill classifies the request (event, external access, enum, or general enhancement), gathers the mandatory information for that type, checks it against the extensibility rules and blockers, drafts the issue against the standard template, and — only after explicit approval — submits it with the `gh` CLI. It is advisory and read-only against workspace code: it never edits, builds, or runs AL source. It applies only to Microsoft base-application AL objects. Runs interactively in VS Code Copilot Chat (agent mode) and the Copilot CLI. TRIGGER when a user wants to request an event, make a member public/global, add or extend an enum, or otherwise ask Microsoft to make base Business Central code more extensible. DO NOT TRIGGER for pure bug reports, for changes to non-Microsoft (custom) objects, or to write or fix AL code.
Update an agent harness used by BC-Bench. Use when bumping GitHub Copilot CLI or Claude Code, reviewing intervening release notes and breaking changes, curating benchmark-worthy model choices, updating the BC-Bench version, or preparing the release handoff.
Implement a single Business Central extensibility request as an AL code change. The request is provided as plain text (a natural-language description of the extension point that is needed, usually a new integration event / event publisher). The skill locates the affected AL code in the current repository, adds the requested extension point following the repository extensibility guidelines, and propagates the change across the W1 base layer and any same-named country/region layer files. It edits only `.al` source files and leaves the changes unstaged in the working tree. No build, no tests, no commit, and no pull request. TRIGGER when the user asks to implement or add an extensibility request / extension point / integration event described in the provided text. DO NOT TRIGGER for bug fixes, for building or testing, or for opening pull requests.
基于 SOC 职业分类
正在显示 SKILL.md
| name | create-release |
| description | Prepare BC-Bench release notes for review. Use when creating a release, screening merged PRs since the previous version tag for changes that may affect evaluation results, matching recent GitHub release notes, or reporting the agent harness and development tool versions shipped by a release. |
Prepare release notes for maintainer review. Do not change versions, commit, tag, push, or create a GitHub release unless explicitly asked.
pyproject.toml and use v<version> as the target tag. If that tag exists, use it as the target ref and select the preceding semantic-version tag. Otherwise, use HEAD as the target ref and select the latest reachable semantic-version tag. Ignore non-version tags such as evaluation-run tags. Exclude uncommitted changes and stop if the range is empty, ambiguous, or not fully available locally.microsoft/BC-Bench. Match their concise paragraph style, spacing, and # Versions section; do not use GitHub's automatically generated notes as the draft.<previous-tag>..<target-ref> range as a merged PR. Review its title, changed files, and PR description, inspecting the diff only as needed to determine whether it may affect evaluation results. Classify every PR as included or omitted, but do not produce a PR-by-PR summary.@github/copilot, @anthropic-ai/claude-code, and Microsoft.Dynamics.BusinessCentral.Development.Tools. Confirm duplicate pins agree. Never copy versions from an older release or infer them from commit messages.Return one fenced markdown block containing the release body for review. Do not include the tag or release title in the body, a commit-by-commit list, PR links, a comparison link, or commentary outside the block.
Use this shape, replacing the placeholders and adding only as many short paragraphs as the changes require:
<Concise summary of evaluation-affecting changes.>
<Optional compatibility or additional impact paragraph.>
# Versions
• GitHub Copilot CLI <version>
• Claude Code <version>
• Microsoft.Dynamics.BusinessCentral.Development.Tools <version>