Agentic.Check 2.4.1

Agentic.Check

agentic.check optimizes your repo for agentic engineering with .NET - based technologies. You run it as dna check.

• Detects which .NET based technologies and features you use
• Recommends an optimal set of agentic directives, skills and tools for those
• You select which to apply
• Directives are installed / updated in AGENTS.md / CLAUDE.md, directly from the dotnet-agentic-engineering GitHub repo
• For Codex, rules that run dotnet outside its sandbox are installed in .codex/rules, so dotnet has network access without approval prompts
• Skills are installed / updated directly from source GitHub skill repo's with gh skill
• Tools that directives and skills depend on are installed / updated with dotnet tool, pinned once per repository; a tool that is already the latest on nuget.org is reported as up to date and left alone

The skills available for composition are carefully tested and are selected from best-in-class GitHub skills repo's:

• dotnet/skills
• unoplatform/studio
• mtmattei/UnoPlatformSkills
• VincentH-Net/dotnet-agentic-engineering

The composition minimizes context usage and avoids contradictions and ambiguities, reducing agent mistakes.

Currently supports foundational agentic habits, .NET, ASP.NET Core, Microsoft Orleans and Uno Platform.

Uno Platform skills are selected depending on detected:

• MVVM or MVUX update pattern
• Pure XAML markup or XAML combined with either Uno C# Markup or C# Markup 2
• Fluent / Material / Simple / Cupertino design system

The .NET CLI end-to-end testing skill is selected when a project interacts with a terminal: it is packaged as a dotnet tool, references a command-line or terminal UI package such as System.CommandLine, Spectre.Console or Hex1b, or reads console input. A console app that only writes output does not qualify.

Prerequisites

• .NET 10 SDK or later (install)
• gh CLI (install)
• Optional: Git (install). Inside a repository that has a .gitignore, the file list comes from git, so ignored output folders are never scanned. Otherwise the folder is walked, skipping bin, obj, TestResults and similar output folders.

GitHub login is optional. Without it, public sources are read anonymously, which is enough for a handful of skills. When GitHub's anonymous rate limit is reached, agentic.check stops and asks you to run gh auth login and rerun; completed changes are kept. When you are logged in, the gh credential is reused for all GitHub requests. Automation can set GH_TOKEN or GITHUB_TOKEN.

Install, update and usage

See Get started