Skip to content
harnesspmv0.5.1
Color scheme
Contrast
Color scheme
Contrast

Ask your agent

In short

  • These prompts work in a repository where npx harnesspm init has run: after Use a harness, or after step 3 of Share a harness. Your agent then has three skills for harnesspm.
  • Each task below has a prompt, what your agent does, and what you decide.
  • The For AI agents part has every step in detail.

The prompts are examples. Use your own words, and your own package names in place of @acme/ui. Keep the word harnesspm in each prompt: it tells your agent which tool and which skill to use.

See what you got

What did harnesspm give you from our dependencies?
Show me `npx harnesspm status`.
  • Your agent lists the packages with a harness, the tools that wait for trust, and the size of the always-on text.
  • You learn what your agent now knows. Each rule in AGENTS.md ends with an ID that names its source.

Turn on a package’s tools

Trust @acme/ui in harnesspm.
  • Your agent adds the package to trust in harnesspm.json and runs npx harnesspm sync.
  • You run npx harnesspm approve in your own terminal. Until then, new hooks, MCP servers and allow rules wait.
  • You decide how far the trust goes: true follows upgrades, and "pin" asks again for each new version. Use "pin" for packages your team does not control. See Trust and safety.

Fix a rule that does not fit

The contrast rule from @acme/colors is too weak for us:
we target WCAG AAA. Change it for this project
with harnesspm.
  • Your agent finds the rule’s source with npx harnesspm why, and adds a patch that changes one section and keeps the rest.
  • You review the change to AGENTS.md in the pull request.
  • When a rule is wrong for everyone, also ask: “Propose this change to the package.” See Change upstream units.

Remember something

Remember this in our harnesspm harness:
we use Conventional Commits in this repository.
  • Your agent writes a rule into the project’s harness. When the note is about how you work everywhere, it goes into your own harness. Without the word harnesspm, an agent may keep the note in its own memory, where your team never sees it.
  • You decide where it belongs, when your agent asks. A project rule reaches the whole team, so it comes as a normal change to review.

Bring your own harness to every repository

Your own rules, notes and skills can live in a repository of yours, and apply on top of any project. Bring your own harness has the prompt that starts one, and what stays with you: you add it in your own terminal, because adding a harness is your trust decision.

Check the setup

Run `npx harnesspm doctor` and tell me what it reports.
  • Your agent runs the checks. doctor changes nothing, and each problem names the command that fixes it.
  • You decide on any fix that changes what git tracks.