github-profile-proof-updaterlisted

# GitHub Profile Proof Updater ## Overview Use this skill to turn a GitHub profile or proof-layer refresh into a repeatable, public-safe workflow: update visuals, preserve working README paths, verify the live page, and create the social/proof trail that explains the update. Do not publish, commit, push, upload, or post externally unless the user explicitly asks for that action. ## Workflow 1. Confirm the target repo and the source asset folder. 2. Inspect the current repo state: - `git status --short` - README image references - target asset filenames and dimensions 3. Preserve existing public paths unless the user asks for a rename in README. - Prefer replacing assets under the old filenames. - Keep known-good hero images unchanged when the user says the hero is already good. 4. Copy or replace only the intended assets. 5. Validate the changed media: - destination files exist - images are readable - dimensions/aspect ratios are plausible for the README layout 6. Re-check README references. - Edit README only if an image path is broken, missing, or intentionally changing. 7. Review the diff and repo status. - Never use broad staging until the changed files are understood. - Prefer staging named files only. 8. If the user asks to commit/push, commit with a focused message and push the current branch. 9. Verify the live GitHub profile or public repo page after push. - Check that all updated visuals render. - Confirm the unchanged her