New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Git Memento Workflow

by mandel-macaque in mandel-macaque/memento

Use git-memento to initialize repository-level AI provider settings, create commits that attach AI session transcripts as git notes, and sync notes to remote.

MITAuto-check passedDevelopment

Install Git Memento Workflow

skills CLI
$ npx skills add mandel-macaque/memento --skill git-memento-workflow -a claude-code

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

GitHub CLI
$ gh skill install mandel-macaque/memento git-memento-workflow --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/mandel-macaque/memento.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/git-memento-workflow .claude/skills/git-memento-workflow && 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
git-memento-workflow
GitHub stars
452
Token cost
~1.2k tokens
SKILL.md length
528 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MIT

At a glance

Use git-memento to initialize repository-level AI provider settings, create commits that attach AI session transcripts as git notes, and sync notes to remote.

  • Works in 7 steps: Preflight → Initialize Once Per Repository → Resolve Session ID → …
  • This skill when users ask to create
  • SKILL.md covers 1. Preflight, 2. Initialize Once Per…, 3. Resolve Session ID and 4. Create Memento Commit or…, plus 3 more sections
  • Calls git

What it does

Git Memento Workflow is an agent skill from mandel-macaque/memento. Use git-memento to initialize repository-level AI provider settings, create commits that attach AI session transcripts as git notes, and sync notes to remote. Trigger this skill when users ask to create or troubleshoot memento commits, configure providers (Codex or Claude), verify note attachment, or share notes with team remotes.

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, covering Git workflow. It works with Git. The repository describes itself as: Keep track of you codex sessions per commit. The licence is MIT.

When your agent uses it

  • This skill when users ask to create
  • Troubleshoot memento commits
  • Configure providers (Codex
  • Verify note attachment

Example prompts

  • “/git-memento-workflow”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Preflight
  2. Initialize Once Per Repository
  3. Resolve Session ID
  4. Create Memento Commit or Amend
  5. Verify Note Attachment
  6. Push Code and Sync Notes
  7. Failure Handling Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit 8543d65. 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

Git Memento Workflow loads about 1.2k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 528 words of instructions outside code blocks.

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

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 mandel-macaque/memento at commit 8543d65, republished under its MIT licence (© mandel-macaque). 528 words, ~1,179 tokens.

Download SKILL.mdSave it as .claude/skills/git-memento-workflow/SKILL.md (or your agent's skills folder).
name
git-memento-workflow
description
Use git-memento to initialize repository-level AI provider settings, create commits that attach AI session transcripts as git notes, and sync notes to remote. Trigger this skill when users ask to create or troubleshoot memento commits, configure providers (Codex or Claude), verify note attachment, or share notes with team remotes.

Git Memento Workflow

Run this workflow whenever work must be committed with an AI session note.

1. Preflight

  • Confirm repository status with git status --short and branch with git branch --show-current.
  • Confirm git memento is available: git memento help.
  • If unavailable, install git-memento into a directory on PATH and re-check.

2. Initialize Once Per Repository

  • Check configuration: git config --local --get memento.provider.
  • If missing, run git memento init codex or git memento init claude.
  • If provider CLI shape differs from expected sessions get/list --json, configure adapter command in local git config:
    • git config --local memento.<provider>.bin <adapter-or-cli-path>
    • git config --local memento.<provider>.getArgs '<args with {id} placeholder>'
    • git config --local memento.<provider>.listArgs '<list args>'
  • For summary mode, configure provider summary execution if defaults do not match your environment:
    • git config --local memento.<provider>.summary.bin <adapter-or-cli-path>
    • git config --local memento.<provider>.summary.args '<args with {prompt}, optionally {skill} and {sessionId}>'

3. Resolve Session ID

  • Prefer explicit session id from the user.
  • For Codex in this environment, default to CODEX_THREAD_ID when present.
  • Validate retrieval before commit by running provider command manually if needed.

4. Create Memento Commit or Amend

  • Stage files as needed (git add ...).
  • Run commit through memento so note attachment happens in the same flow:
    • git memento commit <session-id> -m "<subject>"
    • Optional summary mode: git memento commit <session-id> --summary-skill <skill|default> -m "<subject>"
  • For amend flows:
    • git memento amend -m "<amended-subject>" to carry forward existing note(s) onto the amended commit.
    • git memento amend <session-id> -m "<amended-subject>" to carry forward existing note(s) and append a new session.
    • Optional summary mode: git memento amend <session-id> --summary-skill <skill|default> -m "<amended-subject>"
  • Summary mode behavior:
    • The CLI generates a markdown summary using the configured provider command.
    • It prints the generated summary and requires explicit confirmation.
    • If rejected, it asks for a user prompt and regenerates.
    • It writes the summary into refs/notes/commits and stores the full session in refs/notes/memento-full-audit.
  • Backward compatibility:
    • Legacy single-session notes are preserved.
    • When append is needed, legacy notes are upgraded into the versioned multi-session envelope so no prior session content is lost.
  • For longer body, use embedded newlines in -m or omit -m to use editor.
Show full SKILL.md (188 more words)Show less

5. Verify Note Attachment

  • Read latest commit: git log -1 --pretty=fuller.
  • Show note on that commit: git notes show <commit-hash>.
  • For multi-session notes, expect envelope/version headers and separators:
    • <!-- git-memento-sessions:v1 -->
    • <!-- git-memento-note-version:1 -->
    • <!-- git-memento-session:start -->
    • <!-- git-memento-session:end -->
  • Summary mode stores summary entries in refs/notes/commits and full sessions in refs/notes/memento-full-audit.
  • In summary mode, verify both refs:
    • git notes show <commit-hash> (summary note)
    • git notes --ref refs/notes/memento-full-audit show <commit-hash> (full session)
  • If note is missing, inspect provider command config and rerun commit flow after fixing.

6. Push Code and Sync Notes

  • Push commit branch and sync notes in one step: git memento push <remote>.
  • For default remote, run git memento push.
  • Optional fallback: git push <remote> <branch> then git memento share-notes <remote>.
  • Verify notes exist remotely: git ls-remote <remote> 'refs/notes/*'.
  • notes-sync, notes-rewrite-setup, and notes-carry preserve both refs/notes/commits and refs/notes/memento-full-audit.

7. Failure Handling Checklist

  • git-memento is not configured: run git memento init ....
  • Provider command fails: verify memento.<provider>.* git config and executable permissions.
  • Session not found: list sessions using provider list command and retry with exact id.
  • Note push missing on remote: rerun git memento push <remote> (or git memento share-notes <remote>) and confirm remote ref output.

© mandel-macaque, 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 skills/git-memento-workflow of mandel-macaque/memento.

Open the folder on GitHubat commit 8543d65

Compare with similar skills

Git Memento Workflow 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.

Git Memento Workflow compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Git Memento Workflow this skillmandel-macaque/memento452—~1.2kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost55k—~3.8kAutomated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • 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.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    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.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Migrate Internal Package into Ghost

    TryGhost/Ghost

    Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Git Merge Conflict Resolver

    tailcallhq/forgecode

    Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.

    7.6k GitHub starsUsed in 1 repo~4.5k tokens
    DevelopmentAuto-check passed

More from mandel-macaque/memento

  • Session Summary Default

    mandel-macaque/memento

    Summarize AI coding sessions into concise, privacy-safe markdown focused on implementation-relevant context.

    452 GitHub stars~286 tokensUpdated 6 mo ago
    Auto-check passed

Works with

Categories

Questions about Git Memento Workflow

What does Git Memento Workflow do?

Use git-memento to initialize repository-level AI provider settings, create commits that attach AI session transcripts as git notes, and sync notes to remote. Git Memento Workflow is an agent skill from mandel-macaque/memento. Use git-memento to initialize repository-level AI provider settings, create commits that attach AI session transcripts as git notes, and sync notes to remote.

When should I use Git Memento Workflow?

Git Memento Workflow fits situations like: this skill when users ask to create; troubleshoot memento commits; configure providers (Codex; verify note attachment.

How do I install Git Memento Workflow in Claude Code?

Run `npx skills add mandel-macaque/memento --skill git-memento-workflow -a claude-code`. Or copy the skill folder (skills/git-memento-workflow in mandel-macaque/memento) into .claude/skills/git-memento-workflow in your project. Claude Code loads it when a task matches its description.

How do I install Git Memento Workflow in Codex?

Run `npx skills add mandel-macaque/memento --skill git-memento-workflow -a codex`. Or copy the skill folder (skills/git-memento-workflow in mandel-macaque/memento) into .agents/skills/git-memento-workflow in your project. Codex loads it when a task matches its description.

Can I use Git Memento Workflow 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 mandel-macaque/memento --skill git-memento-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/git-memento-workflow, .gemini/skills/git-memento-workflow, .github/skills/git-memento-workflow and .opencode/skills/git-memento-workflow in your project.

What does Git Memento Workflow need to run?

Going by SKILL.md and its folder, Git Memento Workflow needs the command-line tools its instructions call (git).

Does Git Memento Workflow 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 Git Memento Workflow 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 Git Memento Workflow use?

Git Memento Workflow 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 Git Memento Workflow use?

About 1.2k tokens (SKILL.md is roughly 4.7k 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 Git Memento Workflow?

Skills that share tags, products or a category with Git Memento Workflow: Finishing a Development Branch (obra/superpowers, 296k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Git Memento Workflow?

mandel-macaque (a GitHub user) maintains it in mandel-macaque/memento, which has 452 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on March 12, 2026.

Source: mandel-macaque/memento on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.