From: Andrea Cervesato via ltp <ltp@lists.linux.it>
To: "Andrea Cervesato" <andrea.cervesato@suse.de>,
"Linux Test Project" <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH v4] agents: Add AI agent configuration for code reviews
Date: Wed, 18 Feb 2026 13:52:07 +0100 [thread overview]
Message-ID: <DGI3O8O64JV0.3VFNYUAEVXXFG@suse.com> (raw)
In-Reply-To: <20260217-agents_file-v4-1-e71ae27ea2d9@suse.com>
Hi,
I think this configuration is working pretty well as a starting point.
---
The setup I'm using to test it is the following:
1. install OpenCode from https://opencode.ai/ (npm is the fastest way)
2. open OpenCode in the LTP repo folder
3. configure OpenCode to make sure we can modify the current repo
$ cat .config/opencode/opencode.json
{
"$schema": "https://opencode.ai/config.json",
"permission": {
"*": "ask",
}
}
In this way, we make sure that we have control on what the LLM will
do on our folder. The LLM will ask for permissions when it will
read/write files or download patches in our system.
I know it's possible to give sudo permissions, but it sounds like a
bad idea to me.
4. setup OpenCode in Build mode (TAB), so it's possible to modify the
current folder. This is needed in order to apply patches in the
current LTP directory.
5. CTRL+x-m to select the Model we want to use.
6. provide to the LLM a link to patchwork/lore to start a code review on
a developer patch
7. provide the commit/branch on the local repo if you want to review the
current work you are working on
---
To test this patch, it's better to apply it on a new branch and
explicitly tells to the LLM that we want to always start a review from
this new branch containing the agents configuration. For example,
tells to LLM:
"ALWAYS start a review from the branch <my branch> instead of master"
All reviews will create a new branch starting with "review/" prefix and
they won't be removed lately. In this way, it's possible to review logic
flaws in the patch after an initial LLM review.
---
Please take a look at it and let me know what we can improve. I would
like to merge this patch-set pretty soon in order to start using it and
save a lot of time to review the most common errors.
Kind regards,
--
Andrea Cervesato
SUSE QE Automation Engineer Linux
andrea.cervesato@suse.com
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2026-02-18 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 19:22 [LTP] [PATCH v4] agents: Add AI agent configuration for code reviews Andrea Cervesato
2026-02-18 12:52 ` Andrea Cervesato via ltp [this message]
2026-02-18 12:56 ` Andrea Cervesato via ltp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DGI3O8O64JV0.3VFNYUAEVXXFG@suse.com \
--to=ltp@lists.linux.it \
--cc=andrea.cervesato@suse.com \
--cc=andrea.cervesato@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox