Specsmith Save

Specsmith Save

Saves governance state: backs up the ESDB, commits any staged/unstaged changes, and pushes to the remote.

When to use

• At the end of any work session
• After implementing a feature, fix, or refactor
• After advancing a phase
• Whenever the user says "save", "commit and push", or "specsmith save"

How to run

specsmith save

What it does (in order)

1. ESDB backup — snapshots the epistemic state database
2. Commit — stages all changes and commits with a governance-aware message (or reports "Nothing to commit")
3. Push — pushes the branch to origin (or reports "Everything up-to-date")

Expected successful output

  ✓ esdb_backup: JSON fallback (no WAL to backup)
  ✓ commit: Nothing to commit          ← or a commit hash
  ✓ push: Everything up-to-date        ← or "pushed to origin/branch"

If there are changes to commit

Specsmith auto-stages and commits. You can also pre-stage manually:

git add -A
git commit -m "feat: description

Co-Authored-By: Oz "
specsmith save   # will see nothing to commit, just pushes

Do NOT use git push directly

Always use specsmith save — it ensures the ESDB backup runs before the push, keeping governance state consistent with the remote.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: layer1labs
• Source: layer1labs/specsmith
• License: MIT
• Homepage: https://specsmith.readthedocs.io

Install and usage instructions live in the source repository linked above.