Switch git identity and GitHub account using the gitswitch tool when the user is committing or pushing as the wrong account. Use this skill whenever the user mentions: their commits showing the wrong name/email, pushing to the wrong GitHub account, needing to switch git profiles, wanting to check which git identity is active, getting attribution errors on commits, working across multiple GitHub accounts (personal vs work, multiple clients), or any time the phrase "wrong account" or "wrong identity" appears in a git/GitHub context. Don't wait for the user to say "gitswitch" — if the problem smells like a git identity mismatch, invoke this skill. --- # gitswitch skill `gitswitch` is a terminal tool (installed via Homebrew or curl) that manages multiple local git identities. It switches `git config user.name`, `git config user.email`, the SSH key, and (optionally) the `gh` CLI account — all at once, with one command. ## When to use it Reach for `gitswitch` whenever: - A commit landed with the wrong author name or email - The user is about to push to a work/client repo but is still on their personal identity - The user asks "which git account am I on?" - The user needs to add a new profile for a new job, client, or side project - The user is confused about why `gh` and `git` show different accounts (they're independent) ## Step 1 — Diagnose Always check what's currently active before doing anything: ```bash gitswitch current # shows active profile name + email gitswitch list # shows all profiles, ✓ marks the active one ``` If `gitswitch` is not installed, say so clearly and offer the install instructions: ```bash # Homebrew (recommended): brew install aksisonline/tap/gitswitch # Or, without Homebrew (curl one-liner):
Skill files are scattered across GitHub and communities, difficult to search, and hard to evaluate. SkillWink organizes open-source skills into a searchable, filterable library you can directly download and use.
We provide keyword search, version updates, multi-metric ranking (downloads / likes / comments / updates), and open SKILL.md standards. You can also discuss usage and improvements on skill detail pages.
Sort by downloads/likes/comments/updated to find higher-quality skills.
4. Which import methods are supported?
Upload archive: .zip / .skill (recommended)
Upload skills folder
Import from GitHub repository
Note: file size for all methods should be within 10MB.
5. How to use in Claude / Codex?
Typical paths (may vary by local setup):
Claude Code:~/.claude/skills/
Codex CLI:~/.codex/skills/
One SKILL.md can usually be reused across tools.
6. Can one skill be shared across tools?
Yes. Most skills are standardized docs + assets, so they can be reused where format is supported.
Example: retrieval + writing + automation scripts as one workflow.
7. Are these skills safe to use?
Some skills come from public GitHub repositories and some are uploaded by SkillWink creators. Always review code before installing and own your security decisions.
8. Why does it not work after import?
Most common reasons:
Wrong folder path or nested one level too deep
Invalid/incomplete SKILL.md fields or format
Dependencies missing (Python/Node/CLI)
Tool has not reloaded skills yet
9. Does SkillWink include duplicates/low-quality skills?
We try to avoid that. Use ranking + comments to surface better skills: