mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-12 05:36:40 +00:00
Environment TestandClaude Sonnet 4.6
0b8e16a45d
Add tests/lint/repository/test_markdown_links.py — a hard-fail lint test that scans all git-tracked markdown files for broken relative and repo-root-absolute links. Skips external URLs, anchor-only links, fenced code blocks, and placeholder targets. Apply documentation.md rules to all staged files: add emojis after headlines in docs files, remove emojis from role README headings, standardize Credits sections to the canonical format, remove empty sections and orphaned sentences referring to missing documentation files, fix raw URLs and incorrect link text across role READMEs and docs. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
970 B
970 B
Review Requirements 🔍
You MUST open a Pull Request only when it is ready for real review.
The matching Pull Request template is the SPOT for PR structure, required author input, and review context. You MUST use the guidance in Pull Request Templates and orient your Pull Request to it.
The lint.md page is the SPOT for repository-wide code quality expectations such as diff quality, maintainability, and conventions.
In addition to the templates, keep these repository-wide review rules in mind:
- You MUST keep commit history clear and reviewable.
- Code ownership is defined in CODEOWNERS.
- Auth, proxy, TLS, networking, migrations, and shared abstractions MUST receive extra review attention.
- You SHOULD attach screenshots, traces, logs, and migration notes when they materially help validate the change.
More information here.