Agent skill

Fresh Eyes Amend

by jackfranklin in jackfranklin/dotfiles

Amends the previous commit with current changes, then spawns two subagents to independently review the full git diff and propose fresh commit messages.

MITAuto-check passedDevelopment

Install Fresh Eyes Amend

skills CLI
$ npx skills add jackfranklin/dotfiles --skill fresh-eyes-amend -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jackfranklin/dotfiles fresh-eyes-amend --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/fresh-eyes-amend .claude/skills/fresh-eyes-amend && rm -rf skills-src

Use ~/.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/

Facts

Skill name
fresh-eyes-amend
GitHub stars
255
Token cost
~899 tokens
SKILL.md length
462 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Amends the previous commit with current changes, then spawns two subagents to independently review the full git diff and propose fresh commit messages.

  • Works in 8 steps: Check Status and Stage Changes: Run git… → Capture Old Message: Retrieve and save… → Capture Full Diff: Get the complete diff… → …
  • Tasks that involve Commit messages
  • Calls git
  • Tasks that involve Subagents

What it does

Fresh Eyes Amend is an agent skill from jackfranklin/dotfiles. Amends the previous commit with current changes, then spawns two subagents to independently review the full git diff and propose fresh commit messages. Synthesizes the best parts into a final, accurate commit message without recency bias.

Its SKILL.md is about 900 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, covering Commit messages and Subagents. 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.

When your agent uses it

  • Tasks that involve Commit messages
  • Tasks that involve Subagents

Example prompts

  • “Use the fresh-eyes-amend skill to amend the previous commit with current changes, then spawns two subagents to independently review the full git…”
  • “/fresh-eyes-amend”

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Check Status and Stage Changes: Run git status --porcelain to check for active, unstaged changes. If and only if there are changes to be…
  2. Capture Old Message: Retrieve and save the current commit message
  3. Capture Full Diff: Get the complete diff of the staged changes (and current HEAD) against the parent of HEAD
  4. Spawn Subagents with Zero Context
  5. Synthesize Message
  6. Propose Message to User: Present the synthesized commit message to the user for approval. Do not apply it to the commit automatically.
  7. Apply Approved Message
  8. Report: Confirm to the user that the amend is complete.

What it can do on your machine

Read from SKILL.md and the folder at commit bfc6291. It shows what the files ask for, not the result of running them.

  • Tool permissions

    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.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fresh Eyes Amend loads about 899 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 462 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~899

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.

Safety

Auto-check passed

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.

SKILL.md

The full file from jackfranklin/dotfiles at commit bfc6291, republished under its MIT licence (© jackfranklin). 462 words, ~899 tokens.

Download SKILL.mdSave it as .claude/skills/fresh-eyes-amend/SKILL.md (or your agent's skills folder).
name
fresh-eyes-amend
description
Amends the previous commit with current changes, then spawns two subagents to independently review the full git diff and propose fresh commit messages. Synthesizes the best parts into a final, accurate commit message without recency bias.
disable-model-invocation
true

Fresh Eyes Amend

Use this skill when you want to amend the previous commit and ensure the commit message accurately and unbiasedly reflects the entire combined change.

Workflow

  1. Check Status and Stage Changes: Run git status --porcelain to check for active, unstaged changes. If and only if there are changes to be staged, stage them using appropriate git add commands (e.g., git add -u or git add <file>). Avoid blindly running git add -A unless you intend to include all modified and untracked files in the commit. If there are no changes to stage, proceed to the next step.

  2. Capture Old Message: Retrieve and save the current commit message:

    bash
    git log -1 --pretty=%B

    Keep this as OLD_MESSAGE.

  3. Capture Full Diff: Get the complete diff of the staged changes (and current HEAD) against the parent of HEAD:

    bash
    git diff --cached HEAD~1

    Keep this as FULL_DIFF.

  4. Spawn Subagents with Zero Context: Invoke two parallel subagents using the invoke_subagent tool. Both subagents must receive the identical FULL_DIFF and be instructed to evaluate it with zero prior context.

    • Subagent 1 (FreshEyesReviewer1):
      • Role: Fresh Eyes Reviewer A
      • Prompt:
        You are a fresh-eyes code reviewer. Your only source of information is the git diff provided below. Do not use any other tools to explore the codebase or check git history. Write a high-quality commit message (following standard guidelines: imperative mood, clear summary, explanation of "why" and "how" in the body) that accurately and completely summarizes the changes in this diff. Do not assume any context outside of what is visible in the diff.
        
        CRITICAL: Do NOT include trivial, inane, or self-evident details in the message body (e.g., "added unit tests", "fixed lint errors", "updated imports", "formatted code", "updated build files"). Focus exclusively on the logical "why" and "how" of the change.
        
        Diff:
        <FULL_DIFF>
    • Subagent 2 (FreshEyesReviewer2):
      • Role: Fresh Eyes Reviewer B
      • Prompt: Use the exact same prompt as Subagent 1.
  5. Synthesize Message:

    • Wait for both subagents to return their suggested commit messages.
    • Compare OLD_MESSAGE, the two new proposals, and FULL_DIFF.
    • Synthesize the best parts of the proposals to create a single final commit message that accurately reflects the entire combined change.
    • CRITICAL: Ensure the synthesized commit message NEVER includes trivial, inane, or self-evident details in the body (e.g., "added unit tests", "fixed lint errors", "updated imports", "formatted code", "updated build files"). Focus exclusively on the logical "why" and "how" of the change.
  6. Propose Message to User: Present the synthesized commit message to the user for approval. Do not apply it to the commit automatically.

  7. Apply Approved Message: Once the user approves the message (or provides revisions), apply it and amend the commit:

    bash
    git commit --amend -m "<APPROVED_MESSAGE>"
  8. Report: Confirm to the user that the amend is complete.

© jackfranklin, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in claude/skills/fresh-eyes-amend of jackfranklin/dotfiles.

Open the folder on GitHubat commit bfc6291

Compare with similar skills

Fresh Eyes Amend 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.

Fresh Eyes Amend compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fresh Eyes Amend this skilljackfranklin/dotfiles255—~899Automated safety check: PassMIT
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
ToolJet Multi-Repo CommitToolJet/ToolJet41k—~1.3kAutomated safety check: PassAGPL-3.0
Git Workflow and Versioningaddyosmani/agent-skills105k2 repos~3.5kAutomated safety check: NotesMIT
React Router Pull Request Creatorremix-run/react-router57k—~2.5kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Commits changes across ToolJet's root repo and its server/ee and frontend/ee submodules, writing messages from the diffs and updating submodule pointers in order.

    41k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Git Workflow and Versioning

    addyosmani/agent-skills

    Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.

    105k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check: notes
  • React Router Pull Request Creator

    remix-run/react-router

    Packages finished React Router work into a draft pull request: branch, commit, push, a written PR body and the right GitHub labels.

    57k GitHub stars~2.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Commits changes in the Saleor codebase and works through pre-commit hook failures from ruff, mypy, the GraphQL schema check and the migrations check.

    23k GitHub stars~575 tokensUpdated yesterday
    DevelopmentAuto-check passed

More from jackfranklin/dotfiles

All 21 skills in this repo
  • GitHub Code Review

    jackfranklin/dotfiles

    Perform a thorough, read-only review of one GitHub pull request.

    255 GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Adr

    jackfranklin/dotfiles

    Capture an Architecture Decision Record (ADR) for a significant decision made in the current project.

    255 GitHub stars~962 tokensUpdated yesterday
    Auto-check passed
  • Jack References

    jackfranklin/dotfiles

    Manage Jack's personal technical reference library at ~/git/references.

    255 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Later

    jackfranklin/dotfiles

    Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues.

    255 GitHub stars~767 tokensUpdated yesterday
    Auto-check passed
  • Lexicon

    jackfranklin/dotfiles

    Define, review, and audit a project's domain vocabulary across code and documentation.

    255 GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed
  • Resolve Merge Conflict

    jackfranklin/dotfiles

    A skill your agent uses when you need to resolve an in-progress git merge/rebase conflict.

    255 GitHub starsUsed in 23 repos~427 tokens
    Auto-check passed

Works with

Categories

Questions about Fresh Eyes Amend

What does Fresh Eyes Amend do?

Amends the previous commit with current changes, then spawns two subagents to independently review the full git diff and propose fresh commit messages. Fresh Eyes Amend is an agent skill from jackfranklin/dotfiles. Amends the previous commit with current changes, then spawns two subagents to independently review the full git diff and propose fresh commit messages.

When should I use Fresh Eyes Amend?

Fresh Eyes Amend fits situations like: tasks that involve Commit messages; tasks that involve Subagents.

How do I install Fresh Eyes Amend in Claude Code?

Run `npx skills add jackfranklin/dotfiles --skill fresh-eyes-amend -a claude-code`. Or copy the skill folder (claude/skills/fresh-eyes-amend in jackfranklin/dotfiles) into .claude/skills/fresh-eyes-amend in your project. Claude Code loads it when a task matches its description.

How do I install Fresh Eyes Amend in Codex?

Run `npx skills add jackfranklin/dotfiles --skill fresh-eyes-amend -a codex`. Or copy the skill folder (claude/skills/fresh-eyes-amend in jackfranklin/dotfiles) into .agents/skills/fresh-eyes-amend in your project. Codex loads it when a task matches its description.

Can I use Fresh Eyes Amend in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jackfranklin/dotfiles --skill fresh-eyes-amend -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fresh-eyes-amend, .gemini/skills/fresh-eyes-amend, .github/skills/fresh-eyes-amend and .opencode/skills/fresh-eyes-amend in your project.

What does Fresh Eyes Amend need to run?

Going by SKILL.md and its folder, Fresh Eyes Amend needs the command-line tools its instructions call (git).

Does Fresh Eyes Amend access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Fresh Eyes Amend safe to install?

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.

What licence does Fresh Eyes Amend use?

Fresh Eyes Amend is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fresh Eyes Amend use?

About 899 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fresh Eyes Amend?

Skills that share tags, products or a category with Fresh Eyes Amend: React Router Release Notes Prep (remix-run/react-router, 57k stars), ToolJet Multi-Repo Commit (ToolJet/ToolJet, 41k stars), Git Workflow and Versioning (addyosmani/agent-skills, 105k stars) and React Router Pull Request Creator (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fresh Eyes Amend?

jackfranklin (a GitHub user) maintains it in jackfranklin/dotfiles, which has 255 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 10, 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.