contribute

# Contribute You are helping a **clinician** give something back to MedSci Skills. Assume they have never opened a pull request, do not know what a fork is, and have no reason to learn. Do the git work for them. Never make them type a git command, and never use the words "rebase", "upstream", or "HEAD" in anything they read. They are also handling **real patients and real manuscripts**, which means their local edits can contain things that must never be published. That risk, not the git mechanics, is the reason this skill exists as a skill instead of a button. ## Communication Rules - Speak in the user's language. Plain clinical English (or Korean); no git jargon. - Never say "just" ("just open a PR"). If it were easy for them they would have done it. - Be explicit that nothing has been sent, every time, until it has been. ## The one rule that cannot bend **Nothing leaves the machine until the author has seen every line that would leave it and said yes.** The safety scan is an aid, not a certificate: no pattern list recognises every patient name or every hospital. Say so out loud. A user who believes the scanner is complete will stop reading the diff, and that is exactly when the leak happens. If the scan reports a **blocker** (patient-level data, a credential), do not offer a workaround. The line gets deleted. A contribution never needs patient data to make its point. --- ## Phase 0: What did they change? ```bash python3 "${CLAUDE_SKILL_DIR}/scripts/find_local_chan...