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
- Confirm the target repo and the source asset folder.
- Inspect the current repo state:
git status --short- README image references
- target asset filenames and dimensions
- 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.
- Copy or replace only the intended assets.
- Validate the changed media:
- destination files exist
- images are readable
- dimensions/aspect ratios are plausible for the README layout
- Re-check README references.
- Edit README only if an image path is broken, missing, or intentionally changing.
- Review the diff and repo status.
- Never use broad staging until the changed files are understood.
- Prefer staging named files only.
- If the user asks to commit/push, commit with a focused message and push the current branch.
- Verify the live GitHub profile or public repo page after push.
- Check that all updated visuals render.
- Confirm the unchanged hero remains correct.
- Capture any broken image, stale cache, or layout issue.
- Create or update the proof trail:
- public GitHub links
- commit links or hashes
- asset summary
- LinkedIn/X post links when available
- follow-up checklist
Public Safety Rules
- Do not include local machine paths, private vault structure, raw prompts, logs, credentials, browser cookies, private repo names, account identifiers, or client data in public files.
- Screenshots must not reveal private tabs, emails, analytics, billing, dashboards, file paths, or account menus.
- Social copy should describe outcomes and workflow categories, not private implementation details.
- If a public artifact is being prepared, apply the
github-safe-publisher rules and run its scanner when available.
Social Proof Handoff
When the user wants LinkedIn or X copy for the refresh:
- Lead with the public proof angle.
- Keep LinkedIn reflective and explanatory.
- Keep X shorter, with one idea per post.
- Add alt text for every image.
- Put related X posts into a thread, not scattered comments.
- Track published links in a proof trail or engagement tracker.
Output Format
Return:
- Verdict:
BLOCK, REVIEW, or READY.
- Target repo and files changed.
- Validation performed.
- Live verification result, if applicable.
- Proof/social artifacts created or updated.
- Next recommended action.
1---2name: github-profile-proof-updater3description: Refresh and verify a GitHub profile or public proof layer. Use when the user wants to update GitHub profile visuals, replace README assets while preserving paths, audit profile image references, validate live GitHub rendering, prepare LinkedIn/X proof copy, or document a profile-refresh proof trail.4---56# GitHub Profile Proof Updater78## Overview910Use 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.1112Do not publish, commit, push, upload, or post externally unless the user explicitly asks for that action.1314## Workflow15161. Confirm the target repo and the source asset folder.172. Inspect the current repo state:18 - `git status --short`19 - README image references20 - target asset filenames and dimensions213. Preserve existing public paths unless the user asks for a rename in README.22 - Prefer replacing assets under the old filenames.23 - Keep known-good hero images unchanged when the user says the hero is already good.244. Copy or replace only the intended assets.255. Validate the changed media:26 - destination files exist27 - images are readable28 - dimensions/aspect ratios are plausible for the README layout296. Re-check README references.30 - Edit README only if an image path is broken, missing, or intentionally changing.317. Review the diff and repo status.32 - Never use broad staging until the changed files are understood.33 - Prefer staging named files only.348. If the user asks to commit/push, commit with a focused message and push the current branch.359. Verify the live GitHub profile or public repo page after push.36 - Check that all updated visuals render.37 - Confirm the unchanged hero remains correct.38 - Capture any broken image, stale cache, or layout issue.3910. Create or update the proof trail:40 - public GitHub links41 - commit links or hashes42 - asset summary43 - LinkedIn/X post links when available44 - follow-up checklist4546## Public Safety Rules4748- Do not include local machine paths, private vault structure, raw prompts, logs, credentials, browser cookies, private repo names, account identifiers, or client data in public files.49- Screenshots must not reveal private tabs, emails, analytics, billing, dashboards, file paths, or account menus.50- Social copy should describe outcomes and workflow categories, not private implementation details.51- If a public artifact is being prepared, apply the `github-safe-publisher` rules and run its scanner when available.5253## Social Proof Handoff5455When the user wants LinkedIn or X copy for the refresh:5657- Lead with the public proof angle.58- Keep LinkedIn reflective and explanatory.59- Keep X shorter, with one idea per post.60- Add alt text for every image.61- Put related X posts into a thread, not scattered comments.62- Track published links in a proof trail or engagement tracker.6364## Output Format6566Return:67681. Verdict: `BLOCK`, `REVIEW`, or `READY`.692. Target repo and files changed.703. Validation performed.714. Live verification result, if applicable.725. Proof/social artifacts created or updated.736. Next recommended action.
jqaisystems