test-generator owns all test code generation. This harness does not
duplicate, replace, or invoke it. It improves the input it receives (a
risk-reviewed plan instead of an unreviewed
silently)
Score the context. Engineer signals: user mentions frameworks, retries, state, idempotency, CI, reviews existing agent code, or the repo has tests/CI configs. Builder signals: outcome-focused language ("I want
GitHub Copilot Instructions
This project follows the engineering standard defined in `coding-skills.md`.
Before planning, coding, reviewing, or editing files:
1. Read `coding-skills.md` fully.
2. Read `planning.md` if it exists
auto-loaded by the GitHub Copilot CLI / Copilot app; this file
> is its VS Code counterpart. Both point at the same agent tree — read `AGENTS.md` to route,
> then read
Plan migrations for zero downtime. Add new columns as nullable, backfill, then add constraints.
## CodeReviewReview priority: Correctness, Security, Performance, Maintainability, Testing, Style.
Check for edge cases: empty arrays
Switch between profiles instantly.
- **Snapshots**: Point-in-time captures of deployment state for backup/restore.
### Coding conventions
- **Go 1.25+** with modules. The exact toolchain is pinned once in `go.mod
must follow the team's coding conventions based on BPM repo standards.
## Quick Reference: Coding Style Rules
### File Structure
```csharp
//------------------------------------------------------------
// Copyright (c) Microsoft Corporation. All rights reserved.
//------------------------------------------------------------
using System;
using
reviewed and merged
- The PR ensures all release metadata changes go through codereview
2. **Pull the merged main and tag it:**
```powershell
git checkout main && git pull origin main
write implementation code.
When acting as the reviewer role: You are a senior codereviewer. Compare the diff against what was requested: anything missing, anything extra, anything misunderstood? Then judge
hivelore:allow — ` at
end of line — instead of deleting the rule or rewriting correct code. It covers that line only
and is reported. Repeating it means the scope is wrong
pure TypeScript/JavaScript changes, use ONLY `typescript-reviewer`. For non-TS/JS changes, use ONLY `code-reviewer`. Use `reviewer` only as a final verification check before submitting a PR.
- **Architect
surgical fix
- `/review-change` — fresh-context review of a finished change against its spec
- `/check-drift` — run the mechanical verify + drift checks
- `/create-feature-catalog` — mine the code for a feature → files catalog
- `/perform-feature-add-simulation