Add agent guidance

[Jack Morris (rudolphjacksonm)]

What is being addressed

AzureTRE does not currently provide repository-wide guidance for coding agents or a standard workflow for validating pull requests.

Without this guidance, agents may not consistently:

• Use the appropriate validation commands for each subsystem.
• Respect approval boundaries for deployments and shared Azure environments.
• Test the exact revision associated with a pull request.
• Limit validation and deployment activity to the components affected by a change.
• Report validation results with sufficient evidence.

How is this addressed

• Add AGENTS.md with repository-wide guidance covering:
  • Repository structure and subsystem-specific instructions.
  • Local validation commands.
  • Approval requirements for external side effects, deployments, publishing, destructive actions, and shared-environment testing.
  • Expectations for evidence-based validation and completion reporting.
• Add CLAUDE.md to direct Claude Code to the repository-wide guidance and the appropriate PR-validation workflow.
• Add the pr-tester skill under .claude/skills/pr-tester/ to provide a repeatable AzureTRE pull request validation process that:
  • Resolves and records the exact PR head revision being tested.
  • Prefers isolated worktrees and avoids destructive cleanup or implicit rebasing.
  • Runs local validation before requesting authorization for Azure operations.
  • Scopes builds, deployments, and tests to affected components.
  • Requires explicit authorization before making changes to Azure or other shared environments.
  • Confirms deployed artifacts correspond to the tested revision.
  • Produces a structured validation report with supporting evidence.
• No runtime application behavior is changed.
• No additional product documentation is required because these files document contributor and coding-agent workflows.
• No CHANGELOG.md entry is included because this is repository tooling and contributor guidance rather than a released product change.
• No template version increment is required because no workspace template or deployable component is changed.

Validation

• Confirmed the changes introduce Markdown guidance files only.
• Ran git diff --check successfully.
• Application tests were not run because no application or infrastructure behavior is modified.

No issue number is evident from the branch name or commit, so #<ISSUE_NUMBER> needs replacing. If there is no tracking issue, change the first line to the repository’s accepted no-issue wording
rather than inventing one.

[github-actions]

Unit Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 213fb1c.

♻️ This comment has been updated with latest results.