IHP-Open-PDK
Copilot instructions904 starsChanged 5 months agoApache-2.0View on GitHub
This repository hosts the IHP open-source PDKs (ihp-sg13g2, ihp-sg13cmos5l) and their shared content (ihp-common). The rules for contributions are in CONTRIBUTING.md; read it before reviewing and treat it as the source of truth. Do not restate it here. Review for the rules in CONTRIBUTING.md, in this order of importance: 1. Repository structure (section "Repository structure and multi-PDK rules"). Flag: - new symlinks from one PDK directory into another PDK directory; - absolute symlink targets, or links to gitignored build products;…
The file
We split this copilot-instructions.md into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Do not review the correctness of device models, measurement data, DRC or LVS rule values, or layout geometry.
- Very specific: line 39
Do not comment on Python style.
- Very specific: line 41
Do not treat large generated files (libs.ref/: GDS, CDL, LEF, LIB, Verilog) as hand-written code.
≈ “Common” is an estimate: at least 1 in 5 of the 3,827 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Copilot instructions
This repository hosts the IHP open-source PDKs (ihp-sg13g2,
ihp-sg13cmos5l) and their shared content (ihp-common). The rules for
contributions are in CONTRIBUTING.md; read it before
reviewing and treat it as the source of truth. Do not restate it here.
Reviewing pull requests
Review for the rules in CONTRIBUTING.md, in this order of importance:
- Repository structure (section "Repository structure and multi-PDK
rules"). Flag:
- new symlinks from one PDK directory into another PDK directory;
- absolute symlink targets, or links to gitignored build products;
- files copied between PDKs instead of shared through
ihp-common; - files in an
ihp-<pdk>/directory that are not part of the PDK (build rules, CI helpers, repository tooling); - new top-level directories in a PDK, or tool files outside
libs.tech/<tool>/; - Makefiles inside PDK directories.
- Cross-PDK impact. A change to
ihp-common, or to a file inihp-sg13g2thatihp-sg13cmos5lreaches through a symlink, affects both PDKs. Ask for the tested PDKs to be named if the description does not say so. - Commit messages (section "Commit messages"): title prefixed with the
component path, imperative summary, body explaining the problem, and a
Signed-off-by:trailer on every commit. Point out fix-up commits that should be squashed. - Housekeeping: a
CHANGELOG.mdentry for user-visible changes, the Apache-2.0 license header on new source files, and README/docs updates when behaviour a user relies on changes.
Scope
- Do not review the correctness of device models, measurement data, DRC or LVS rule values, or layout geometry. These come from the foundry and are verified by the regression workflows, not by review.
- Do not comment on Python style;
flake8(configured in.flake8) and the non-ASCII check in CI already cover it. - Do not treat large generated files (
libs.ref/**: GDS, CDL, LEF, LIB, Verilog) as hand-written code. Check only that they are in the right place and named for the right PDK.
Language
Comments are read by contributors from several companies. Be concrete: name the file, the rule from CONTRIBUTING.md that is affected, and what would resolve it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

