contributions▌

Create maintainer-friendly pull requests while avoiding 16 common rejection mistakes. \n \n Prevents personal development artifacts (SESSION.md, planning docs, debug screenshots, temp test files) from being committed using a pre-PR check script \n Enforces three critical workflow rules: always use feature branches, test thoroughly before submitting, and keep PRs focused on a single change under 400 lines \n Provides templates and guides for PR descriptions using What/Why/How structure, conventio

When asked to find all files a specific author contributed to on a branch (compared to main or another upstream), follow this procedure. The goal is to produce a simple table that both humans and LLMs can consume.