Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Other skills

companion-docs

Where to put a document that belongs with a repository but must not be committed to it: a translation or annotated copy of one of its files (for example a Traditional Chinese version of an English doc in a repository you cannot commit personal documents to (an employer's, a client's)), or a note about the repository that maps to no single file (an evaluation, a review write-up, a hand-off). Use when the user asks for a translation or a version of a document in another language, in any language however they name it (中文版, 日本語版, 한국어판, en français; examples only), a companion or side-by-side version of a document, a note / write-up / evaluation about a repository that should not be committed to it, when reading a document that may already have one, or when the user mentions a companion, or memsaga's data repo by any name (the memories repo, memsaga KB, memsaga memory, memsaga data, memsaga memories) and its companion/ directory. Not for a request to reply in some language (answer in Japane

grimmerk · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add grimmerk/memsaga --skill companion-docs

About this skill


name: companion-docs description: "Where to put a document that belongs with a repository but must not be committed to it: a translation or annotated copy of one of its files (for example a Traditional Chinese version of an English doc in a repository you cannot commit personal documents to (an employer's, a client's)), or a note about the repository that maps to no single file (an evaluation, a review write-up, a hand-off). Use when the user asks for a translation or a version of a document in another language, in any language however they name it (中文版, 日本語版, 한국어판, en français; examples only), a companion or side-by-side version of a document, a note / write-up / evaluation about a repository that should not be committed to it, when reading a document that may already have one, or when the user mentions a companion, or memsaga's data repo by any name (the memories repo, memsaga KB, memsaga memory, memsaga data, memsaga memories) and its companion/ directory. Not for a request to reply in some language (answer in Japanese, reply in French), which is about the conversation language, not a document."

Companion docs

A companion is a file that belongs with a repository but must not land in it. Two kinds:

  • A companion of one file: a translation, a commentary, a summary of a specific document. Its path mirrors the source's path.
  • A note about the repository: an evaluation, a review write-up, a hand-off, anything tied to the repository (or to several of its files, a PR, an issue) but not to one file. It lives under _notes/.

Both live in the memsaga data repo, which commits them automatically at the end of the turn.

Path convention

<memsaga repo>/companion/<repo name>/<path inside that repo>.<lang>.md
  • <memsaga repo> is the data repository, the path memsaga repo prints (~/git/memories in the examples here).
  • <repo name> is the last component of the source repository's path (webapp for ~/git/webapp or ~/code/webapp), not the GitHub full name. The same repository on two machines shares that name, which is the point. Two different repositories with the same name (~/git/webapp and ~/code/webapp on one machine) would collide: when the existing companions' sources point into another folder, use <parent>-<name> (code-webapp) for the new repository.
  • <path inside that repo> keeps the source's relative path and extension, then adds the language tag: docs/architecture.md -> docs/architecture.zh-tw.md. The tag is the companion's language (zh-tw, ja, de, fr); the examples below use zh-tw because that is the author's case, not a rule.

Example: the companion of ~/git/webapp/docs/architecture.md is ~/git/memories/companion/webapp/docs/architecture.zh-tw.md.

Notes about a repository

<memsaga repo>/companion/<repo name>/_notes/<name>.md

<name> is short and descriptive (open-code-review-evaluation.md, pr-2107-review.md). Frontmatter is the same as for any companion (see Frontmatter below) with two differences: type: Note, and relates_to listing what it concerns (files relative to the repository, PRs and issues as owner/repo#N) in place of sources. A note has no source file for a later session to read, so add the same one-line pointer to the repository's MEMORY.md as for a draft (below), and keep it while the note is still useful.

---
type: Note
title: open-code-review evaluation
description: Whether open-code-review could replace the bot reviewers on webapp
relates_to:
  - docs/review-process.md
  - acme/webapp#2107
generated:
  by: claude-code/claude-opus-5-5
  at: 2026-09-30T10:00:00Z
status: stable
---

When the source does not exist yet

A document may be drafted in the companion language first (a design written in Traditional Chinese to discuss before any English version exists) in a repository where it cannot be committed. Use the same path rule with the path the source will have once it is written, so the companion is found the day the source appears: ~/git/memories/companion/webapp/docs/new-design.zh-tw.md for a future ~/git/webapp/docs/new-design.md. Set status: draft and leave sources empty; fill sources in when the source is committed. Ask the user where the source will live if it is not obvious.

A draft has no source file for a later session to read, so also add one line to that repository's auto-memory index (MEMORY.md under ~/.claude/projects/<slug>/memory/): the topic, the companion's path, and "no source yet". The pointer is what a fresh session in that repository loads; the content stays in the companion. Remove the line once the source is committed, since the path rule finds the companion from then on.

Frontmatter

Every companion starts with YAML frontmatter following the Open Knowledge Format core fields plus provenance, so the source and its version are recorded and any OKF consumer can read it:

---
type: Translation            # or Commentary, Summary; Note for _notes/ (with relates_to instead of sources)
title: architecture (zh-TW)
description: Traditional Chinese translation of webapp docs/architecture.md
sources:
  - resource: ~/git/webapp/docs/architecture.md
    last_modified: 2026-09-18T09:12:00Z     # commit time of the source revision translated
    commit: 3f9a85f6                         # source repo commit the companion was made from
generated:
  by: claude-code/claude-fable-5-1
  at: 2026-09-18T10:05:00Z
status: stable                               # draft | stable | deprecated
---

Get the source commit with git -C <source repo> log -1 --format='%h %cI' -- <path>.

When writing

  1. Resolve the companion path from the source path as above; create parent directories as needed.
  2. Write the frontmatter, then the content. Keep headings parallel to the source so the two files can be read side by side.
  3. Do not add anything to the source repository, its .gitignore, or its do
Read the complete source ↗