admin: Add AI coding assistant configuration#5206
Conversation
|
Anybody have opinions about this? I'm especially interested in hearing from anybody who juggles multiple coding agents to give a sanity check for whether I'm on the right track with how to set up the directories and links to accommodate several tools and have them share as much as possible with minimal repetition. |
|
Take 2: minimal checked-in components, script to do per-tool setup. Change of strategy. Instead of checking in links and other niceties
A script can be invoked by users to do the local setup of links or Currently supported tools by this script include Claude Code, |
|
Last chance. Will merge tomorrow if there are not objections forthcoming. |
Adds agent configuration supporting Claude Code, Cursor, GitHub Copilot, OpenAI Codex, and Opencode. A single AGENTS.md and contents of .agents subdirectory serve as the canonical source for instructions, skills, and other things that can be used across multiple tools. To avoid duplication, tool-specific files are, whenever possible, either symbolic links or thin wrappers referring to canonical areas. Includes per-directory .gitignore files to prevent accidental commits of per-user settings and session data. This initial commit includes two skills that I wrote and have used for the last couple monthly releases: release-notes-update and prepare-patch-release. I assume that we will add more over time as we discover tasks that we want to make standard skill automation for. Note that our use symlinks is a little troublesome on Windows, and assumes that Windows-based developers will (a) enable Windows Developer Mode, and (b) `git config --global core.symlinks true`, both prior to cloning the repo. I think that if you don't do that, Windows developers will get separate copies of those files rather than links, in their local tree. But I think even that doesn't really matter for people not changng these very files. Assisted-by: Claude Code / claude-sonnet-4-6 The AGENTS.md, Claude skills, and general scheme are entirely from me. I used Claude to help me establish the setup for the other tools I don't happen to use. Signed-off-by: Larry Gritz <lg@larrygritz.com>
Change of strategy. Instead of checking in links and other nicities
specific to tools, ONLY check into the repo:
* AGENTS.md - general repo-level agent instructions
* .agents/ - directory with skills, etc., shared by all tools
A script can be invoked by users to do the local setup of links or
references to allow them to use a particular tool. For example,
.agents/setup-agent claude
Currently supported tools by this script include Claude Code,
Codex, Cursor, GitHub Copilot, and OpenCode.
Signed-off-by: Larry Gritz <lg@larrygritz.com>
lgritz
force-pushed
the
lg-agents
branch
2 times, most recently
from
699660b to
c37fffa
Compare
Signed-off-by: Larry Gritz <lg@larrygritz.com>
1 participant
Adds agent configuration supporting Claude Code, Cursor, GitHub
Copilot, OpenAI Codex, and Opencode. A single AGENTS.md and contents
of .agents subdirectory serve as the canonical source for
instructions, skills, and other things that can be used across
multiple tools.
A script can be invoked by users to do the local setup of links or
references to allow them to use a particular tool:
.agents/setup-agent TOOLCurrently supported tools by this scriptinclude Claude Code, Codex, Cursor, GitHub Copilot, and OpenCode.
This initial commit includes two skills that I wrote and have used for
the last couple monthly releases: release-notes-update and
prepare-patch-release. I assume that we will add more over time as we
discover tasks that we want to make standard skill automation for.
Assisted-by: Claude Code / claude-sonnet-4-6
The AGENTS.md, Claude skills, and general scheme are entirely from me.
I used Claude to help me establish the setup script for the other
tools I don't happen to use.