Use this skill for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro. Review Python MCP server changes, KiCad adapter and tool-contract changes, tests, npm/package wrappers, Tauri/Rust desktop code, GitHub Actions, security controls, documentation, generated metadata, and compatibility/release surfaces. Use it whenever reviewing a PR or diff in this repository, especially changes under src/, tests/, packages/, src-tauri/, .github/workflows/, or public MCP…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# KiCad MCP Pro Code Review
Review pull requests for **correctness, security, contract stability, compatibility,
test coverage, and release safety**. Prefer a small number of high-confidence,
actionable findings over broad style feedback.
KiCad MCP Pro is a production MCP server that drives real KiCad projects. Treat
unsafe mutations, incorrect tool contracts, path/subprocess mistakes, protocol
regressions, and misleading engineering verdicts as high-risk.
## Review stance
- Review the changed code and the behavior introduced by the change.
- Comment on unchanged code only when the PR newly makes an existing defect reachable
or materially increases its impact.
- Do not invent failures, tool behavior, KiCad behavior, CI results, or browser evidence.
- Distinguish a demonstrated defect from a possible improvement.
- Prefer correctness and user-impact findings over formatting or naming nits already
enforced by repository tooling.
- Do not require a broad refactor when a focused fix addresses the defect.
- If no actionable defect is found, do not manufacture a comment.
## 1. Gather review context first
Before writing findings:
…
The line at the top of this page pins the label git:20260813.f3397ad, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_4loryhp3uvrcdcig
GET https://markdownregistry.com/api/v1/resolve?ref=oaslananka/kicad-mcp-pro/code-review
GET https://markdownregistry.com/api/v1/blob/83fa49d527a1a1abce88422ff0c5cccef9c27a825ba49396653795927696ae40
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
oaslananka/kicad-mcp-pro · .agents/skills/visual-excellence/SKILL.md · Drive a KiCad schematic to a professional, cosmetically clean state through a score → fix → render → verify loop using…
oaslananka/kicad-mcp-pro · .agents/skills/wired-subcircuit-design/SKILL.md · Build a genuinely wired, showcase-grade KiCad schematic with KiCad MCP Pro — wired sub-circuit islands plus a tidy…
kyegomez/swarms · examples/single_agent/capabilities/skills/multiple_skill_dirs/team_skills/code-review/SKILL.md · Review Python code for bugs, missing tests and security issues using the team's shared standards
basicmachines-co/basic-memory · .agents/skills/code-review/SKILL.md · Use when reviewing Basic Machines code for house style, architecture risk, pre-merge hardening, or whether a change…
nteract/semiotic · .github/skills/code-review/SKILL.md · Review Semiotic pull requests for behavioral bugs, regressions, contract drift, and missing evidence. Use for GitHub…
cbrock84/headcount · plugins/technology/skills/code-review/SKILL.md · Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review…
