pull-requestlisted

# Pull Request Skill ## When to Use - Contributing to any repository via PR (external or internal) ## Principles 1. **Minimal change** — Touch only what's necessary for the feature/fix 2. **Follow their conventions** — Their style, not ours 3. **Atomic PR** — One PR = one feature/fix. Never mix concerns 4. **Read first, code second** — CONTRIBUTING.md, README (how to contribute section), existing PRs ## Workflow ### 1. Read Their Rules ```bash cat CONTRIBUTING.md .github/CONTRIBUTING.md README.md 2>/dev/null | head -200 git -C /full/path log --oneline -20 # commit message style git -C /full/path branch -r | head -20 # branch naming ls .github/PULL_REQUEST_TEMPLATE* 2>/dev/null ``` ### 2. Bypass Our Claude Code Hooks for External Projects Our Claude Code hooks (ruff auto-format, line-limit, pytest-fullpath, git-C enforcement) WILL corrupt external codebases by reformatting their files to our style. This is the #1 source of dirty PRs. **Offending hooks (defined in `.claude/hooks/settings.json`):** - PostToolUse `format_code.sh` — ruff/black auto-format on Write|Edit - PostToolUse `run_lint.sh` — linter auto-fix on Write|Edit - PreToolUse `limit_line_numbers.sh` — blocks files >512 lines - PreToolUse `enforce_pytest_fullpath.sh` — blocks relative pytest paths - PreToolUse `enforce_git_dash_C.sh` — blocks git without -C flag **Solution: Start Claude Code with `cc --disable-hooks`** This sets `CLAUDE_CODE_DISABLE_HOOKS=true` via `_cld_start_session` in `~/.bash.d/all/0