git.sr.ht/~berg/llm-agent (link)

commit signals (0)

none

source signals (4)

• AGENT.mdvia agents-md

  # AGENT.md
  
  Guidance for coding agents working in this repository.
  
  ## Project
  
  `llm-agent` is an Emacs Lisp coding agent that runs in an Emacs buffer. It
  streams model responses, executes tool calls, maintains sessions and transcripts,
  and supports snapshots, subagents, MCP servers, worktrees, and commit workflows.
  
  Runtime requirements:
  
  - Emacs 29.1 or newer
  - `curl`
  - No required third-party Emacs packages
  
  Optional packages and programs enable additional behavior: `yaml` for
  file-defined agents and ski

• .skills/elisp-development/SKILL.mdvia unspecified

  ---
  name: elisp-development
  description: Emacs Lisp development best practices including file templates, project structure, testing, and coding style. Use when writing Emacs Lisp packages or configuration.
  ---
  
  # Emacs Lisp Development Skill
  
  ## When to Use
  - Writing new Emacs Lisp packages
  - Developing Emacs configuration
  - Creating Emacs extensions or modes
  - Writing tests for Elisp code
  - Setting up CI/CD for Elisp projects
  
  ## Core Guidelines
  
  ### File Template
  All Elisp files must follow the standard t

• .skills/version-bump/SKILL.mdvia unspecified

  ---
  name: version-bump
  description: Analyze commits since the latest version tag and bump the version according to semver rules. Use when preparing a release or whenever the user asks to determine or apply a version bump. Reads commit messages, updates CHANGELOG.md, and optionally creates the new tag.
  ---
  
  # Version Bump
  
  Determine the appropriate semantic version bump by analyzing commits since the latest git tag, update CHANGELOG.md with feature-oriented summaries, then optionally create the new tag.
  
  ## 

• .skills/clean-code/SKILL.mdvia unspecified

  ---
  name: clean-code
  description: Readability review for Emacs Lisp based on "Clean Code" (Robert C. Martin), adapted to elisp idioms. Use after implementing or changing .el files — at the end of a feature or milestone, before a commit — and whenever the user asks to refactor, clean up, simplify, or improve readability or naming. Complements the elisp-development skill, which owns file templates, project structure, and testing mechanics.
  source: "Adapted for Emacs Lisp from ClawForge (https://github.com

ignorefile signals (0)

none