Skip to content

feat(rf-mind): add community plugin for robotframework-mind - #18

Open
ai94iq wants to merge 2 commits into
MarketSquare:mainfrom
ai94iq:feat/rf-mind
Open

ai94iq wants to merge 2 commits into
MarketSquare:mainfrom
ai94iq:feat/rf-mind

Conversation

@ai94iq

@ai94iq ai94iq commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

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 main with only plugins/rf-mind and the regenerated files (no rf-maestro content). Install line uses uv add. Follows 5.0.0: rf-core dependency by name, no metadata.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

  • Robot Framework capabilities go through robotcode; gaps are reported upstream.
  • Generated files were regenerated with their command, not edited by hand: python scripts/build-catalog.py and python 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.

@manykarim

Copy link
Copy Markdown
Collaborator

Hi @ai94iq 👋
While I really like the idea behind robotframework-mind- I have the impression most of its features to find and list tests based on different search criteria is already covered by robotcode discover.
https://robotcode.io/guides/cli/discovering-tests/

We would really like to have such core capabilities for test case searches focused on robotcode.
Sorry that this is not clearly documented in the repo yet - will do that as soon as possible.

Let's check if there is anything which is not part of robotcode yet and raise and issue for it if needed.
https://github.com/robotcodedev/robotcode/issues
https://github.com/robotcodedev/robotcode/blob/main/AI_POLICY.md

@ai94iq

ai94iq commented Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

@manykarim thanks, fair point. I compared robotframework-mind with robotcode 2.8.0 discover.

Already in robotcode:

  • finding tests by ticket key or tag (--search, -i), with file:line

Not in robotcode yet. Output below is from the robotframework-mind test fixture:

  • keyword definitions in .resource files, each duplicate with its args
$ python -m robot_mind kw "Open Profile Browser"
keyword  Open Profile Browser  collections/cases_page.resource:5  - Same name as the common one, defined again here.
keyword  Open Profile Browser  resources/common.resource:11  (${profile}, ${headless}=${True})  - Opens a browser on a fresh profile.
  • call sites of a keyword inside other keywords and in setup/teardown, at the call line
$ python -m robot_mind callers "Query Items"
keyword  Open Authenticated Browser  resources/common.resource:20
test  Cases Page Cleans Up  tests/cases.robot:16
test  Cases Page Cleans Up  tests/cases.robot:18

discover tests --search "Query Items" returns only the test. --search "Open Authenticated Browser" gives no match, because only another keyword calls it.

  • variables from *** Variables *** and VAR with their values, and the keywords that use them
$ python -m robot_mind find /api/items/query
(one JSON hit from docs/ trimmed)
var  ${ENDPOINT_ITEMS_QUERY}  resources/common.resource:5  = /api/items/query
keyword  Query Items  resources/common.resource:22  - POST ${ENDPOINT_ITEMS_QUERY}

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.

@manykarim

Copy link
Copy Markdown
Collaborator

Hi @ai94iq, thank you for the detailed comparison with robotcode discover above! It's really helpful, and it found real gaps that are worth closing.

As I mentioned earlier, we want core capabilities like finding tests, keywords and callers to live in robotcode, so every agent and editor benefits. Since then we've written this down as "RobotCode first" in AI_POLICY.md. The policy came after your PR, so you couldn't have known it, but it now applies to all open PRs. robotframework-mind parses .robot and .resource files itself, and the skill asks agents to use it before other lookups (SKILL.md:15), so as it stands it would overlap with the robotcode skills.

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 robotcode

You 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:

  • callers of a keyword, in other keywords and in setup/teardown;
  • variables from *** Variables *** and VAR, with their values and the keywords that use them.

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 become

Once 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:

  • base it on main with only plugins/rf-mind and the regenerated files; this branch also contains feat(rf-maestro): add community plugin for MaestroLibrary #17;
  • for the install line, use the project's tool (uv add) rather than a bare pip install;
  • add the "AI assistance" section from the PR template. Your comment above already shows the kind of line we mean.

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! 🎉

@manykarim

Copy link
Copy Markdown
Collaborator

Hi @ai94iq, a short update: 5.0.0 is out. If you reshape this PR later, plugin.json gets no version of its own (python scripts/build-catalog.py writes the shared one), and the dependency is just "dependencies": ["rf-core"] without a range. The rest of my last comment stays the same: we keep this PR open while the robotcode issues are discussed. Thanks! 🙂

@ai94iq

ai94iq commented Nov 20, 2026

Copy link
Copy Markdown
Contributor Author

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 uv add, and the AI assistance section is in the description.

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.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants