Working with a coding agent
Precept ships two things for a coding agent that writes tests in your project:
- The MCP server answers questions the project cannot answer for itself: which environment a run will use, why a green build found no tests, what a filter selects.
- The skills are the workflows: the steps to add a test, debug a run, migrate a suite, upgrade Precept and set up a pipeline. Each is one task, not one module — the API itself the agent reads from the MCP server and these pages. A Copilot agent and an instructions file come with them.
The skills are published as autom3tion/precept-skills
in the Agent Skills format, which GitHub Copilot, Claude Code, Cursor and
other agents that read SKILL.md files understand:
npx skills add autom3tion/precept-skills
| Skill | The agent loads it when |
|---|---|
precept-writing-tests |
Adding or changing a test, a Gherkin step, or the setting or registration it needs. See Writing tests and Assertions. |
precept-debugging-runs |
A run fails, finds no tests, lists them twice or ignores a setting. See Running. |
precept-migrating |
Moving a suite in from NUnit, xUnit, MSTest, SpecFlow, FluentAssertions, Selenium or RestSharp. |
precept-upgrading |
Moving the suite to a newer Precept. See Upgrading. |
precept-pipelines |
Running the suite on Azure Pipelines with the shipped pipeline and job template. |
The installer only adds. After an update that removes a skill, delete the precept-* folders that
are no longer in the published set.
GitHub Copilot#
Copy .github/agents and .github/instructions from the published repository into your own
.github/ folder, and put the skills under .github/skills/. The installer above already puts them
there for Copilot.
The Precept agent declares the MCP server itself, launched with dnx Precept.Mcp, so a project
that adopts the agent needs no separate MCP configuration. The agent loads the skill for the task,
follows its steps, and finishes by running what it changed.
Keeping them in step#
The skills name Precept's API: the entry points, the assertions, the settings keys. They are versioned with Precept. The published README says which Precept version it describes, and every release republishes them.
Use the version your project references. If the MCP server reports a different version, trust the project's: that is the code the agent will compile against.