Repository navigation
Conversation
|
Hi @ai94iq 👋 We would really like to have such core capabilities for test case searches focused on Let's check if there is anything which is not part of robotcode yet and raise and issue for it if needed. |
|
@manykarim thanks, fair point. I compared robotframework-mind with robotcode 2.8.0 Already in robotcode:
Not in robotcode yet. Output below is from the robotframework-mind test fixture:
Those three are where the library still adds something. Happy to raise them on robotcode, or keep this PR parked, your call. AI/tooling disclosure: this comparison and reply were prepared with help from Claude Code. I reviewed the text and the output above. |
|
Hi @ai94iq, thank you for the detailed comparison with As I mentioned earlier, we want core capabilities like finding tests, keywords and callers to live in Your work on robotframework-mind is a great starting point for getting these features into robotcode, and I'd love to see that happen. Bring the gaps to robotcodeYou already have the examples. Each gap could be one issue at https://github.com/robotcodedev/robotcode/issues, with your fixture output as the "today vs. wanted" part. For example: Title: discover: list keyword definitions, including duplicates
Wanted: `robotcode discover keywords "Open Profile Browser"` prints every definition with file:line
and arguments, and flags names defined more than once:
Open Profile Browser resources/common.resource:11 (${profile}, ${headless}=True)
Open Profile Browser collections/cases_page.resource:5 duplicate name
Today: `robotcode discover` lists tests, tasks, suites and tags, not keyword definitions.The same shape works for the other two:
robotcode welcomes contributions under its own AI_POLICY.md, and since you've already solved the parsing, a PR there may be a natural next step. I'm happy to support the issues. What this PR could becomeOnce robotcode has one of these commands, a small skill or a few lines in rf-language that teach agents when to use it would be very welcome here. Until then, could you link the robotcode issues in this PR? We'll keep it open while they're discussed, then decide together whether to reshape it or start fresh. When you update the branch:
Thanks again for the great reply and for the AI disclosure in it! 🙂 PS: I merged #13, #14, #15 and #16 today. I made a few small adjustments myself so they could go in right away; each PR's last comment lists them. Thanks for those! 🎉 |
|
Hi @ai94iq, a short update: 5.0.0 is out. If you reshape this PR later, |
Install line uses uv add.
|
Thanks @manykarim. I opened the three robotcode issues: robotcodedev/robotcode#698, robotcodedev/robotcode#699, robotcodedev/robotcode#700. The branch is rebased on main with only plugins/rf-mind and the regenerated files, the install line uses |
Eval coverage needs a narrow task, a partial-install task and a trigger set for every shipped skill; counts rf-mind in the partial-install test.
What this changes
Adds
rf-mind, a community-tier plugin with one skill for robotframework-mind. Parked while the gaps it covers are raised in robotcode:Rebased on
mainwith onlyplugins/rf-mindand the regenerated files (no rf-maestro content). Install line usesuv add. Follows 5.0.0:rf-coredependency by name, nometadata.version.AI assistance
Claude Code (Claude Opus) made the edits and ran the checks. I reviewed the diff and the check output, and I have the right to submit it.
Before you open it
robotcode; gaps are reported upstream.python scripts/build-catalog.pyandpython scripts/build-agent-variants.py.For the reviewer
Maintainer per catalog.yaml: @ai94iq. Local checks: installer, description, structure and command suites green; catalogue, governance, skill validation, plugin references and docs voice pass.