new official type: "agent"

[gsemet]

Hello

With the advent of coding agent (Claude Code, Copilot), I often update in-project prompts, skills, constitution. I use the build or chore types but it is not exactly the same role. For me:

• build: relates to the toolchain that transform the source code into deliverables
• ci: relates to how this toolchain is adapted in CI + extra CI stuff
• chore: relates to maintainance stuff.

ai is too short and conotted, i like agent, it is generic enough.

Examples:

• agent: refine progressive disclosure ordering in AGENTS.md
• agent(memory): split memory bank into thematic blocks
• agent(prompts): rewrite python coding guidelines for haiku models

[sedoia09-boop]

Здравствуйте

С появлением агентов для написания кода (Claude Code, Copilot) я часто обновляю подсказки, навыки и структуру проекта. Я использую типы build или chore, но это не совсем то же самое. Для меня это:

• build: относится к набору инструментов, которые преобразуют исходный код в готовые продукты
• ci: относится к тому, как этот набор инструментов адаптируется для непрерывной интеграции + дополнительные функции CI
• chore: относится к задачам по сопровождению.

ai Слишком короткое и запутанное, мне нравится agent, оно достаточно универсальное.

Примеры:

• agent: refine progressive disclosure ordering in AGENTS.md
• agent(memory): split memory bank into thematic blocks
• agent(prompts): rewrite python coding guidelines for haiku models

[heysailboat]

I've just been putting <agent name: codex | claude | antigravity/gemini > | in front of all my commits. So, commits would look like this:

• codex | feat: add new information column
• claude | fix: debug Spotify API calls
• gemini | docs: update contributors section

[xeruf]

Personally I believe that is overdoing it - too many types make the whole convention shaky especially when contributors come in. Karma actually replaced chore with build and I agree duplicating them bloats the type list around types of changes that are rare in the first place.

So I would settle for one of chore or build (build seems to be establishing itself, maybe because chore sounds deterring) and than use scopes for everything else: build(ci), build(agents), builder(gradle) etc, or memory which is more on the documentation side maybe as docs type.

@heysailboat that is a totally different issue - the original issue was talking about modifying agent config, you are talking about documenting which agent did something - which I definitely think does not belong into the short commit message because it does not help you understand what was done, thats why most agents default to footers already

[heysailboat]

@xeruf Thanks for pointing that out. I didn't quite understand the original issue entirely and assumed it referred to documentation. My comment can be ignored.