How do I install the Attic Git skill?

Run npx skillmds@latest add nishikantaray/attic-git-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Attic Git safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Attic Git?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Attic Git free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Attic Git?

NishikantaRay (@nishikantaray) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Attic Git by nishikantaray — Agent Skill

Name: Attic Git
Author: NishikantaRay

Attic Git

Everything about .attic/ and git: fixes merge conflicts in INDEX.md and DECISIONS.md by installing a union merge driver, and sets up a shared attic for a team. Use whenever git and .attic/ appear in the same problem: "merge conflicts in INDEX.md", "the attic keeps conflicting", "conflict in DECISIONS.md", "share the attic with my team", "commit the attic", "onboard someone to our attic".

File contents

Attic and git

First, in the same shell command as anything below, locate the script:

ATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)

.attic/INDEX.md and DECISIONS.md are append-only, so two branches that each stash something will conflict on every merge. The fix is a union merge driver.

Add to the repository's .gitattributes (create it if absent):

.attic/INDEX.md merge=attic
.attic/DECISIONS.md merge=attic

Each developer runs this once per clone. Git does not allow a repository to configure a driver command for security reasons, so this cannot be automated for them:

git config merge.attic.name "attic union merge"
git config merge.attic.driver "node <path-to-plugin>/scripts/attic-merge.js %O %A %B %P"

Resolve <path-to-plugin> from $(dirname "$ATTIC_JS")/../../.. and show the real path in the command you print.

Verify by describing the check, or running it in a scratch clone: two branches each appending an item should merge with no conflict markers.

Then tell the user what to commit, from docs/TEAM.md:

Commit .attic/INDEX.md, .attic/items/, .attic/DECISIONS.md for shared memory.
Consider gitignoring .attic/items/session-*.md, which are personal working state and rarely useful to others.
A committed attic is in git history. If a credential ever reaches it, rotating the credential is the fix. Removing the file is not enough.

If someone declines the merge driver, warn them that conflicts on INDEX.md will be frequent and that resolving them by picking one side silently loses the other side's items.

---name: attic-git-2description: Everything about .attic/ and git: fixes merge conflicts in INDEX.md and DECISIONS.md by installing a union merge driver, and sets up a shared attic for a team. Use whenever git and .attic/ appear in the same problem: "merge conflicts in INDEX.md", "the attic keeps conflicting", "conflict in DECISIONS.md", "share the attic with my team", "commit the attic", "onboard someone to our attic".license: MIT---# Attic and gitFirst, in the same shell command as anything below, locate the script:```bashATTIC_JS=$(ls -d "${CODEX_HOME:-$HOME/.codex}"/plugins/cache/attic/attic/*/skills/attic/scripts/attic.js "${CODEX_HOME:-$HOME/.codex}"/skills/attic/scripts/attic.js "$HOME"/.agents/skills/attic/scripts/attic.js .agents/skills/attic/scripts/attic.js 2>/dev/null | sort -V | tail -1)````.attic/INDEX.md` and `DECISIONS.md` are append-only, so two branches thateach stash something will conflict on every merge. The fix is a union mergedriver.1. Add to the repository's `.gitattributes` (create it if absent):```.attic/INDEX.md merge=attic.attic/DECISIONS.md merge=attic```2. Each developer runs this once per clone. Git does not allow a repository to configure a driver command for security reasons, so this cannot be automated for them:```bashgit config merge.attic.name "attic union merge"git config merge.attic.driver "node <path-to-plugin>/scripts/attic-merge.js %O %A %B %P"``` Resolve `<path-to-plugin>` from `$(dirname "$ATTIC_JS")/../../..` and show the real path in the command you print.3. Verify by describing the check, or running it in a scratch clone: two branches each appending an item should merge with no conflict markers.Then tell the user what to commit, from `docs/TEAM.md`:- **Commit** `.attic/INDEX.md`, `.attic/items/`, `.attic/DECISIONS.md` for shared memory.- **Consider gitignoring** `.attic/items/session-*.md`, which are personal working state and rarely useful to others.- **A committed attic is in git history.** If a credential ever reaches it, rotating the credential is the fix. Removing the file is not enough.If someone declines the merge driver, warn them that conflicts on INDEX.mdwill be frequent and that resolving them by picking one side silently losesthe other side's items.

Frequently asked questions