Skip to content
Agentmart
Submit a tool

AGENTS.md · s-kostyaev/ellama

AGENTS.md from s-kostyaev/ellama: 34 lines covering Git Workflow, Code Style Guidelines, Operation Guidelines.

Template by s-kostyaev

IndexedGPL-3.0★ 963
Write a review

Install

Works with Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Claude Code. Read the repository before you give any tool access to your data.

curl -fsSL https://raw.githubusercontent.com/s-kostyaev/ellama/main/AGENTS.md -o AGENTS.md

Read it and adapt it to your project before use.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

The AGENTS.md file that s-kostyaev/ellama (963 stars) keeps for coding agents. It has 34 lines in 3 sections: Git Workflow; Code Style Guidelines; Operation Guidelines. Use it as a model for your own project's instructions.

Use cases: code-generation, version-control

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

What's in it

An AGENTS.md file: instructions coding agents (Codex, Cursor, Copilot, Gemini CLI and others) read before working in a repo.

For
Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Claude Code
Length
34 lines
File
AGENTS.md

Sections

  1. Git Workflow
  2. Code Style Guidelines
  3. Operation Guidelines

First lines (shown under the repo's GPL-3.0 license)

# AGENTS.md – Agentic Coding Quick Reference

## Git Workflow

Before committing, use the project-local `commit-message` skill.

Never merge, rebase, cherry-pick, or otherwise integrate code into `main`.
Never push directly to `main`; always use a feature branch and a pull request.

For release work, use the project-local `changelog` skill.

For documentation changes intended for users, use the `humanize-writing` skill
before finalizing the text.  This applies to README, NEWS, manuals, guides, and
user-facing docs.  Preserve technical names, command names, option names, and
document structure.

## Code Style Guidelines

- Keep `require`s grouped at the file top.
- Use `kebab-case`; symbols should be prefixed with `ellama-`, or
  `ellama-{subpackage}-` in subpackages.  In `ellama-tools.el` tool specs use
  `snake_case`.
- Wrap risky calls in `(condition-case err ...)` and signal with `(error "msg")`
  when appropriate.
- Comments use `;;` for buffer comments.

## Operation Guidelines

1. ALWAYS use available tools to make user requested action. Carefully fill all
   required fields.
2. Double quotes escaping: use one backslash (`\`) before quotes.
3. ALWAYS use the `oq` skill to inspect `.org` files such as `README.org` and
   `NEWS.org`; they are large enough that structure-first queries are required.

Signals

Stars
963
Forks
65
Open issues
22
Last commit (this folder)
Jun 25, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
GPL-3.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from s-kostyaev

Cite this page

AGENTS.md · s-kostyaev/ellama. Agent Mart. https://agentmart.dev/templates/s-kostyaev-ellama-agents-md (last updated 2026-10-24)