L0Lmaker opened a new pull request, #3417:
URL: https://github.com/apache/tinkerpop/pull/3417

   ## Summary
   
   - The current template `Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] 
[TOOL2]` is being interpreted inconsistently — at least two contributors have 
placed the model family in the agent slot and the IDE/CLI in brackets, when the 
intended structure (per @spmallette) is `<agent>:<model>` with brackets 
reserved for auxiliary tools.
   - Names each placeholder explicitly and adds three concrete examples in the 
prose covering the common single-agent case and the rarer auxiliary-tool case.
   - Style matches the rest of AGENTS.md — inline backticks throughout, no 
fenced or indented code blocks introduced.
   
   ## Context
   
   Raised by @spmallette on 
[#3416](https://github.com/apache/tinkerpop/pull/3416#issuecomment-4363617916):
   
   > I'd envisioned: `Assisted-by: Claude Code:claude-opus-4-7` ... I might 
need to better define that to get what I want there. It's interpreting the 
"tool" to be Claude Code - maybe because the tool is not seen as optional??
   
   This PR addresses that by naming each placeholder and providing examples 
that demonstrate the intended form. The bracket interpretation in the new 
wording — "auxiliary tools beyond the primary agent" — reflects my reading; 
happy to revise if a different meaning is preferred.
   
   ## Branches
   
   `AGENTS.md` exists only on `master`, so this is master-only.
   
   ## Test plan
   
   - [x] Renders correctly on GitHub
   - [x] No fenced or indented code blocks introduced — existing AGENTS.md 
prose-with-inline-backticks style preserved
   - [x] All in-prose examples conform to the new format
   
   ## Notes
   
   This change was AI-assisted; the commit's `Assisted-by:` trailer 
demonstrates the new format.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to