biopass
CLAUDE.md602 starsChanged 14 days agoMITView on GitHub
Multi-modal biometric login (face + fingerprint) for Linux. Full guide: CONTRIBUTING.md. Show the output; don't just claim it passes. Run what the change touches: Before opening or updating a PR, run /pre-pr. It does the checks above, a fresh-context review against REVIEW.md, and /security-review for high-risk paths. All AI review runs locally; GitHub CI only runs the mechanical checks.
In this repositoryOne other file it gives its agents.
- pre-prSkill
The file
We split this CLAUDE.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Before opening or updating a PR, run /pre-pr.
- Very specific: line 27
Never test PAM changes on the host's real /etc/pam.d — use a VM (see CONTRIBUTING "System Lockout Warnings").
- Very specific: line 29
Don't add dependencies or change auth/install/packaging/PAM flows without a linked discussion.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
Biopass
Multi-modal biometric login (face + fingerprint) for Linux. Full guide: CONTRIBUTING.md.
Layout
auth/— C++20 / CMake. PAM module (auth/pam:libbiopass_pam.so+biopass-helper), face (ONNX Runtime), fingerprint, sharedcore. libcamera is built from source and bundled (auth/BundleLibcamera.cmake).app/— Tauri v2 desktop app. React + Vite + TypeScript + Tailwind inapp/src, Rust inapp/src-tauri(linksauth/build/fingerprint/libbiopass_fingerprint.a).app/src-tauri/scripts/— deb/rpm post-install scripts, PAM config, ld config. Shipped to users as root.docs/— PAM, Polkit, IR camera docs.
Verify before saying "done"
Show the output; don't just claim it passes. Run what the change touches:
| Area | Command |
| Frontend | cd app && bun run lint && bunx tsc --noEmit |
| Rust | cd app/src-tauri && cargo fmt --all --check && cargo clippy --all-targets -- -D warnings && cargo test (needs make build-auth and app/dist from bun run build) |
| C++ | make build-auth and clang-format --dry-run --Werror on changed auth/**/*.{cc,h} |
| Packaging | make package |
Before opening or updating a PR, run /pre-pr. It does the checks above, a fresh-context review against REVIEW.md, and /security-review for high-risk paths. All AI review runs locally; GitHub CI only runs the mechanical checks.
Rules
- Never test PAM changes on the host's real
/etc/pam.d— use a VM (see CONTRIBUTING "System Lockout Warnings"). - PAM code must fail closed: any error →
PAM_AUTH_ERR/PAM_IGNORE, neverPAM_SUCCESS. - Don't add dependencies or change auth/install/packaging/PAM flows without a linked discussion.
- PR descriptions and issues may be AI-drafted. Follow
.github/PULL_REQUEST_TEMPLATE.md/.github/ISSUE_TEMPLATE/, keep every heading, facts and real output only. - Conventional commits:
fix(scope): …,feat(scope): …,chore: …. - Review checklist and known recurring issues: REVIEW.md.
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.

