# Cmd Session Commit

> Capture learnings from the current coding session and update AGENTS.md. Use when the user asks to close the loop, run session-commit, record best practices, or update agent instructions based on recent work.

- **Type:** Skill
- **Install:** `agentstack add skill-olshansk-agent-skills-cmd-session-commit`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [Olshansk](https://agentstack.voostack.com/s/olshansk)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [Olshansk](https://github.com/Olshansk)
- **Source:** https://github.com/Olshansk/agent-skills/tree/main/skills/cmd-session-commit

## Install

```sh
agentstack add skill-olshansk-agent-skills-cmd-session-commit
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Session Commit

Analyze the current coding session, propose improvements to `AGENTS.md`, and apply approved changes.

## Workflow

1. Read the current `AGENTS.md` and build a mental map of existing sections.
2. If the repo documents a validation or repair command for instruction files, run it before proposing edits.
3. Extract only durable learnings from the current session.
4. Propose changes using the format in `references/change-proposal-format.md`.
5. Wait for explicit user approval before applying any edits.
6. Apply approved changes and merge with existing content.

## What to capture

- Coding patterns and conventions established in the session
- Architecture decisions and reasoning that should persist
- Debugging playbooks and recurring gotchas
- Workflow preferences that improve future sessions

## Guardrails

- Do not capture transient implementation details that will age quickly.
- Prefer updating existing sections before creating new headings.
- Use concise bullet points rather than long paragraphs.
- Keep guidance tool-agnostic unless behavior differs by tool.
- If no meaningful learning occurred, report that and stop.

## Pointer file behavior

If `CLAUDE.md`, `CODEX.md`, or `GEMINI.md` are missing or empty, create symlinks that point to `AGENTS.md`.

## Output contract

- Proposal stage: output only proposed changes with explicit add/modify/remove counts.
- Apply stage: update `AGENTS.md` only after explicit approval.
- Completion stage: summarize what changed and where.

## Source & license

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

- **Author:** [Olshansk](https://github.com/Olshansk)
- **Source:** [Olshansk/agent-skills](https://github.com/Olshansk/agent-skills)
- **License:** MIT

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

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-olshansk-agent-skills-cmd-session-commit
- Seller: https://agentstack.voostack.com/s/olshansk
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.