Review and Checkpoint Workflow
Use Git as the review layer for AI-driven D365FO edits, and use `d365fo review diff` for a shallow BP-style probe (missing EDT/Label, hard-coded strings, dynamic query) over changed AxTable/AxClass XML on top of the raw byte diff. Invoke whenever the user is about to start a non-trivial change, before "accepting" AI edits, or wants a quick heuristic pass over what changed.
Install
npx skills add dynamics365ninja/d365fo-cli --skill review-and-checkpoint-workflowgit clone --depth 1 https://github.com/dynamics365ninja/d365fo-cli.git /tmp/d365fo-cli
mkdir -p ~/.claude/skills
cp -r /tmp/d365fo-cli/skills/anthropic/review-and-checkpoint-workflow ~/.claude/skills/review-and-checkpoint-workflowPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
> ⛔ **NEVER write X++ AOT XML files directly** via PowerShell, terminal file commands (`Set-Content`, `Out-File`, `New-Item`), editor write tools, or any raw text approach. The XML schema (`<AxClass>`, `<AxTable>`, `<AxForm>`, `<Methods>`, `<SourceCode>`) is proprietary — LLMs have not been trained on it reliably. **ALWAYS use `d365fo generate …` commands** to produce correct AOT XML. If `d365fo` is unavailable in PATH, stop and ask the user to install it. # Git-checkpoint review workflow > Visual Studio 2022 has no inline accept/reject UI for AI edits. Use Git as > the review layer; pair with `d365fo review diff` for a quick heuristic > probe on top of the raw byte diff. ## 1. Before starting any non-trivial task ```sh # Either: clean tree + a fresh branch git switch -c d365fo/<short-task> # Or: at minimum, a checkpoint commit on the current branch git commit -am "checkpoint before <task>" ``` Do NOT create branches autonomously without telling the user — propose, wait, then execute. ## 2. During the task Every `d365fo generate … --overwrite` writes a `.bak` next to the original so you can recover the previous version if Git history isn't enough. After each scaffold or edit, run a quick `git diff` to confirm the change is contained. For AOT XML, the diff must be additive or narrowly targeted. If unrelated XML nodes disappear, the edit is wrong and must be reverted before continuing. Treat removals of `<DataSourceModifications>`, `<DataSourceReferences>`,
Details
- Skill name
review-and-checkpoint-workflow- Repository
- dynamics365ninja/d365fo-cli
- Path
skills/anthropic/review-and-checkpoint-workflow/SKILL.md- Repo updated
- 16 November 2026
FAQ
What does the Review and Checkpoint Workflow skill do?
Use Git as the review layer for AI-driven D365FO edits, and use `d365fo review diff` for a shallow BP-style probe (missing EDT/Label, hard-coded strings, dynamic query) over changed AxTable/AxClass XML on top of the raw byte diff. Invoke whenever the user is about to start a non-trivial change, before "accepting" AI edits, or wants a quick heuristic pass over what changed.
How do I install the Review and Checkpoint Workflow skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add dynamics365ninja/d365fo-cli --skill review-and-checkpoint-workflow. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Review and Checkpoint Workflow popular?
It lives in dynamics365ninja/d365fo-cli, which has 49 GitHub stars and 26 forks.
Related skills
Analytics and Er
49dynamics365ninja/d365fo-cli
Model the D365FO analytical and document-generation surfaces — aggregate measurements and the entity store, tiles/cues and KPIs, and Electronic Reporting (ER). Invoke when the user asks about a workspace tile, a KPI, an aggregate measurement, the entity store, Power BI content, or running/binding an ER format.
Barcode Scanning
49dynamics365ninja/d365fo-cli
Barcodes and scanner input in D365FO — printing vs scanning are unrelated code paths, GS1-128 application identifiers, item-barcode resolution, and where the platform parses a scan for you. Invoke when the user mentions barcodes, GS1, GTIN, SSCC, scanning, scanners, item barcodes, or barcode setup.
Build Error Triage
49dynamics365ninja/d365fo-cli
Turn a D365FO compiler, best-practice, or runtime error into the specific fix it calls for. Invoke when the user pastes a build log, an xppc message, a BP violation, or an infolog stack trace and asks what it means or how to fix it.
Workflow Authoring
49dynamics365ninja/d365fo-cli
Build a D365FO workflow — the workflow template, its document class, approvals and tasks, the submit menu item, and the generated event handlers. Invoke when the user asks to create an approval workflow, add a workflow to a table or form, or wire canSubmitToWorkflow.
Generalist Playbook
49toffyui/ccteams
Operational playbook for stack-agnostic feature work — fixed-order stack detection, vertical-slice delivery, a catalog of unfamiliar-codebase mistakes (phantom utils, pattern drift, generated files, invented commands), and verification using only the project's own commands. Read in full at the start of every task on this team.
Working Method
49toffyui/ccteams
Frontier-grade engineering working method — goal compression, ground truth before opinion, hypothesis discipline, execution as evidence, honest reporting, exit checklist. Read in full at the start of any non-trivial task; inject the digest into every delegation prompt.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.