Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Manage Jack's personal technical reference library at ~/git/references.
$ npx skills add jackfranklin/dotfiles --skill jack-references -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jackfranklin/dotfiles jack-references --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/jack-references .claude/skills/jack-references && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "jack-references" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/jack-references into .claude/skills/jack-references/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jack-references", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/jack-referencesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jackfranklin/dotfiles --skill jack-references -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jackfranklin/dotfiles jack-references --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/skills/jack-references .agents/skills/jack-references && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jack-references" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/jack-references into .agents/skills/jack-references/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jack-references", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jackfranklin/dotfiles --skill jack-references -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jackfranklin/dotfiles jack-references --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/skills/jack-references .cursor/skills/jack-references && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jack-references" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/jack-references into .cursor/skills/jack-references/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jack-references", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jackfranklin/dotfiles.git --path claude/skills/jack-references--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jackfranklin/dotfiles --skill jack-references -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jackfranklin/dotfiles jack-references --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/skills/jack-references .gemini/skills/jack-references && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jack-references" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/jack-references into .gemini/skills/jack-references/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jack-references", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jackfranklin/dotfiles jack-referencesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jackfranklin/dotfiles --skill jack-references -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/skills/jack-references .github/skills/jack-references && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jack-references" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/jack-references into .github/skills/jack-references/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jack-references", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jackfranklin/dotfiles --skill jack-references -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jackfranklin/dotfiles jack-references --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/skills/jack-references .opencode/skills/jack-references && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jack-references" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/jack-references into .opencode/skills/jack-references/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jack-references", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
jack-referencesManage Jack's personal technical reference library at ~/git/references.
Jack References is an agent skill from jackfranklin/dotfiles. Manage Jack's personal technical reference library at ~/git/references. Use for searching/reading existing references, or adding new ones. Invoke with /jack-references and optional keywords to search, or when the user wants to save a new reference guide. PROACTIVELY suggest saving a new reference whenever the conversation involves figuring out how a library, API, or tool works — especially after debugging, reading docs, or solving a non-obvious integration problem. A good prompt — "Want me to save this as a…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Git. The repository describes itself as: My dotfiles for my dev environment, compromising of tmux, vim, zsh and git. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 48208f5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
gitghFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Jack References loads about 1.2k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 463 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jackfranklin/dotfiles at commit 48208f5, republished under its MIT licence (© jackfranklin). 463 words, ~1,217 tokens.
.claude/skills/jack-references/SKILL.md (or your agent's skills folder).Personal technical reference library at ~/git/references. Each file is a focused Markdown cheatsheet for a library, API, or tool.
First, resolve the absolute path to the references repo:
echo $HOME/git/referencesUse the output of this command (e.g. /home/jack/git/references) as the literal path for all subsequent commands in this skill. Never use $HOME again after this step — always substitute the resolved absolute path.
Check if the repo exists:
ls $HOME/git/references/.git 2>/dev/null && echo "exists" || echo "missing"If missing: clone it:
mkdir -p $HOME/git
gh repo clone jackfranklin/references $HOME/git/referencesIf it exists: fetch and check if a pull is needed:
git -C $HOME/git/references fetch origin main --quiet
git -C $HOME/git/references rev-parse HEAD
git -C $HOME/git/references rev-parse origin/mainIf the hashes differ, pull:
git -C $HOME/git/references pull --ff-only origin mainIf they match, skip the pull.
The user provided: $ARGUMENTS
Split into individual search terms. If $ARGUMENTS is empty, infer relevant keywords from the current task or conversation context (e.g. the library, API, or technology being discussed).
Run two searches and deduplicate.
Search A — filename match:
ls $HOME/git/references/*.md 2>/dev/nullA file matches if any search term appears in its name after treating hyphens as word separators. For example, "speech" matches browser-speech-to-text.md; "genai" matches google-genai.md.
Search B — content grep (case-insensitive, filenames only):
For each search term:
grep -ril "TERM" $HOME/git/references/Combine results from A and B, removing duplicates. Keep only .md files.
If more than 4 files matched, prefer files that matched on both filename and content, then filename-only, then content-only. Read the top 4.
Use the Read tool to read each matched file in full. Reference files are intentionally small and self-contained — always read the complete file, never truncate.
If the search returned nothing, list all available reference files:
ls $HOME/git/references/*.md 2>/dev/nullDisplay as a bullet list (strip the path prefix and .md suffix for readability) and ask the user which one to read, or pick the most likely candidate based on context.
Explain which file(s) you found and why they're relevant, then present the full reference content in a way that directly addresses the current task. Do not summarize or truncate — complete, accurate reference material is the deliverable.
If multiple files matched, separate their contents with a heading per file.
Use this when the user wants to save a new reference guide, or when you've just figured out how something works and it's worth capturing for future use.
Use lowercase kebab-case based on the topic: <technology-or-topic>.md. Examples: openai-responses-api.md, deno-kv.md, css-container-queries.md.
Check it doesn't already exist:
ls $HOME/git/references/<proposed-name>.md 2>/dev/null && echo "exists" || echo "new"If a file already exists for this topic, offer to update it instead of creating a duplicate.
Reference files follow this structure:
# <Title>
Brief one-line description of what this is.
## Key concepts / API
...focused, practical content...
## Examples
...real usage examples...
## Gotchas / notes
...anything non-obvious...Keep it dense and practical — these are personal cheatsheets, not tutorials. No padding.
Use the Write tool to create $HOME/git/references/<filename>.md.
git -C $HOME/git/references add <filename>.md
git -C $HOME/git/references commit -m "add <filename>"
git -C $HOME/git/references push origin mainConfirm the push succeeded and report the filename back to the user.
© jackfranklin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in claude/skills/jack-references of jackfranklin/dotfiles.
Open the folder on GitHubat commit 48208f5
Jack References next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jack References this skilljackfranklin/dotfiles | 255 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Codebase Knowledge Graph Q&AEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Code Design Rationale Investigatorcursor/plugins | 10k | 9 repos | ~2.6k | Automated safety check: Pass | None | |
| Understand Diff AnalysisEgonex-AI/Understand-Anything | 86k | 1 repos | ~1.4k | Automated safety check: Pass | MIT |
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Egonex-AI/Understand-Anything
Answers questions about a codebase by searching a prebuilt knowledge graph of its files, functions, classes and dependencies, not by rereading every source file.
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
Egonex-AI/Understand-Anything
Gives an in-depth explanation of one file, function or module by reading the project's knowledge graph and checking that the graph is still fresh.
jackfranklin/dotfiles
Perform a thorough, read-only review of one GitHub pull request.
jackfranklin/dotfiles
Capture an Architecture Decision Record (ADR) for a significant decision made in the current project.
jackfranklin/dotfiles
Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues.
jackfranklin/dotfiles
Scaffold a new Deno 2 + Hono + Deno KV + Eta + HTMX app with password auth and PWA support.
jackfranklin/dotfiles
A skill your agent uses when you need to resolve an in-progress git merge/rebase conflict.
jackfranklin/dotfiles
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Works with
Categories
Manage Jack's personal technical reference library at ~/git/references. Jack References is an agent skill from jackfranklin/dotfiles. Manage Jack's personal technical reference library at ~/git/references.
Jack References fits situations like: searching/reading existing references; adding new ones; wants to save a new reference guide.
Run `npx skills add jackfranklin/dotfiles --skill jack-references -a claude-code`. Or copy the skill folder (claude/skills/jack-references in jackfranklin/dotfiles) into .claude/skills/jack-references in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jackfranklin/dotfiles --skill jack-references -a codex`. Or copy the skill folder (claude/skills/jack-references in jackfranklin/dotfiles) into .agents/skills/jack-references in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jackfranklin/dotfiles --skill jack-references -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jack-references, .gemini/skills/jack-references, .github/skills/jack-references and .opencode/skills/jack-references in your project.
Going by SKILL.md and its folder, Jack References needs the command-line tools its instructions call (git and gh).
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Jack References is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Jack References: Finishing a Development Branch (obra/superpowers, 296k stars), Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars), Codebase Knowledge Graph Q&A (Egonex-AI/Understand-Anything, 86k stars) and Code Design Rationale Investigator (cursor/plugins, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jackfranklin (a GitHub user) maintains it in jackfranklin/dotfiles, which has 255 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 7, 2026.
Source: jackfranklin/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.