Microsoft AzureKnown publisherAzure/azclips/AGENTS.md

azclips

AGENTS.md15 starsChanged 2 days agoMITView on GitHub

Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository13 other files it gives its agents.
- Agent/AGENTS.mdAGENTS.md
- .azure-pipelines/AGENTS.mdAGENTS.md
- devops/scripts/AGENTS.mdAGENTS.md
- azclips-custom-code-classifierSkill
- azclips-scenario-test-converterSkill
- extension-test-coverageSkill
- migrate-clips-to-extensions-codegen-llm-hybridSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill

The file

We split this AGENTS.md into the rules it gives an agent

11 rules. About 1 is common, 6 are distinctive, and 4 are very specific to this project.

≈1
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific
could be automatic: a setting could enforce it

Very specific:
Use the .NET SDK pinned in global.json.
line 4
Very specific:
Run targeted tests with dotnet test <test-project>.csproj.
line 6
Distinctive:
Keep changes focused and avoid unrelated refactors.
line 7
Distinctive:
Use C# with nullable enabled and implicit usings.
line 19
Distinctive:
Follow existing naming, namespace, and folder conventions.
line 20
Distinctive:
Prefer dependency injection and existing helpers over manual wiring.
line 21
Distinctive:
Add or update tests for behavior changes.
line 22
Very specific:
Import module manifests from src/PS/<Module>/<Module>.psd1 during local development.
line 26
Very specific:
Use build/Set-ModuleConfiguration.ps1 when staging modules under artifacts/<Configuration>/PS.
line 27
Common:
Do not commit secrets or local-only configuration.
line 38
Distinctive:
Keep pull requests small and include validation notes.
line 40

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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

AGENTS.md

Repository Guidelines

Essentials

Use the .NET SDK pinned in global.json.
Build with dotnet build azclips.slnx.
Run targeted tests with dotnet test <test-project>.csproj.
Keep changes focused and avoid unrelated refactors.

Project Layout

src/ contains product code and shared build props.
src/Core/ contains core framework libraries.
src/Extensions/ contains extension projects.
src/PS/ contains PowerShell module projects and manifests.
tests/ contains xUnit test projects and fixtures.
tools/ contains repository tooling.
docs/ and wiki/ contain documentation.

Coding Guidelines

Use C# with nullable enabled and implicit usings.
Follow existing naming, namespace, and folder conventions.
Prefer dependency injection and existing helpers over manual wiring.
Add or update tests for behavior changes.

PowerShell Modules

Build the solution before importing binary-backed modules.
Import module manifests from src/PS/<Module>/<Module>.psd1 during local development.
Use build/Set-ModuleConfiguration.ps1 when staging modules under artifacts/<Configuration>/PS.

DevOps & CI/CD

For Azure DevOps pipeline YAML (.azure-pipelines/), see .azure-pipelines/AGENTS.md.
For build/packaging/signing/publishing scripts (devops/scripts/), see devops/scripts/AGENTS.md.
These scoped guides are the source of truth for pipelines and scripts; prefer them over this file for DevOps work.

Agent

For the AI agent under Agent/ and its tests, see Agent/AGENTS.md.

Safety

Do not commit secrets or local-only configuration.
Preserve existing public behavior unless the task explicitly changes it.
Keep pull requests small and include validation notes.

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.

Check your setup, free