agentleFS
le4kerle4ker/mneme-template/.agents/skills/sync-vault/SKILL.md

sync-vault

Skill2 starsChanged 14 days agoMITView on GitHub

Commit vault changes and push them to the configured Git remote.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check Git status. Stage all vault changes, including added, modified, renamed, and deleted files.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- markdownlint-disable MD041 -->

Check Git status. Stage all vault changes, including added, modified, renamed, and deleted files. Exclude local settings and memory files. Write a concise commit message that describes the structure of the change, not sensitive note contents.

Examples:

ChangeCommit message
Log entry addedAdd log entry
Note updatedUpdate note
New note in an AreaAdd note
Multiple AreasUpdate vault notes

The pre-commit hook formats and lints staged Markdown. If it fails, fix all reported issues and retry. Then push to the configured remote. If there is nothing to commit, push any existing commits. Report the commit created, number of commits pushed, and whether the remote is up to date.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.