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 12 stars 1 forks Updated 2 days ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
37
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
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
6 months ago
Last Updated
2 days ago
Language
C#
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

dotnet-techne-code-review

Use when reviewing PRs/diffs/branches/documents for .NET quality, correctness, performance, security, data access, messaging, and observability. Includes adversarial critical-thinking mode for skeptical/cynical review requests. Keywords: code review, review PR, review diff, critical review, cynical review, adversarial review, production readiness, low GC, AOT, security review.

12 Updated 2 days ago
Metalnib
Code & Development Solid

code-review

Multi-agent code review with parallel specialized reviewers, architecture validation, challenge validation, and durable handling of previously decided findings. Use `rq` to request a review of diffs (defaults to main branch), `rs` to respond to findings and record intentional non-fix decisions beside the relevant code. Triggers on "review this", "review my code", "code review", "check for bugs", "audit this", when examining PRs, pull requests, branches, or diffs. Always asks user before applying fixes or adding decision comments.

46 Updated 1 months ago
martinffx
Testing & QA Solid

dotnet-techne-qa-pipeline

Use when the user asks to verify a story or ticket implementation against its spec - per-AC verdicts, code reuse and design conformance, dead code, then adversarial maintainer verification. Requires the qa/review agent roles registered by scripts/install-codex.sh. Keywords: story QA, acceptance criteria, spec conformance, AC coverage, QA this branch, verify story.

12 Updated 2 days ago
Metalnib