dotnet-techne-review-pipeline

Solid

Use when the user asks for a multi-agent .NET code review - five parallel reviewers (correctness, performance, security/observability, data/messaging/integration, generalist) plus an adversarial maintainer that refutes weak findings. Requires the review agent roles registered by scripts/install-codex.sh. Keywords: dotnet review pipeline, multi-agent review, parallel reviewers, maintainer pushback, review this branch, cynical review.

Data & Documents 11 stars 0 forks Updated today MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
36
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# .NET review pipeline (multi-agent) You are the orchestrator. Do not review the code yourself - dispatch, then format the result. Paths below are relative to this skill's base directory. The checklists, scripts, and contracts live in the sibling review skill: `../../../skills/dotnet-techne-code-review/`. ## Step 0 - Check the budget, then the roles A full run spends **six agent turns** - five reviewers plus the maintainer - on top of your own context. That is the point (independent lanes, fresh-context falsification), but it is not free. Before fanning out, say in one line what the run will cost and offer the cheaper path when it fits: a diff under ~5 files with no security, public-API, data or messaging surface, or a user on a constrained plan, is better served by the single-context `dotnet-techne-code-review` skill. If the user wants the pipeline but not the full cost, drop lanes explicitly and name which and why - never silently review less than you claim. The roles: `review-correctness`, `review-performance`, `review-security-observability`, `review-data-messaging`, `review-generalist`, `review-maintainer`. ## Step 0b - Check the roles exist List your available agent roles. If the `review-*` roles are missing, stop and tell the user to run `scripts/install-codex.sh` from the plugin, and use the `dotnet-techne-code-review` skill for a single-context review in the meantime. ## Step 1 - Resolve target and mode - Target: a branch name, commit range, staged changes,...

Details

Author
Metalnib
Repository
Metalnib/dotnet-episteme-skills
Created
4 months ago
Last Updated
today
Language
C#
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category