nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can Jira Coding Agent auto-discovers & registers skills from a nested test project directories?

Swati Singh

As documented, Jira Coding Agent skills auto-discovery happens only at repository root .rovodev/skills, not recursively when the session starts. Is there a way for Jira Coding Agent to auto-register skills from the nested test project's .rovodev/skills folder or “additional skill dirs” setting?

Accepted answers

Mihai_LeanZero

No setting for it, as far as the docs go. The Rovo Dev skills page has the built-in ones plus two folder locations, user (~/.rovodev/skills or ~/.agents/skills) and project (.rovodev/skills or .agents/skills at the root). The config.yml settings list has no skills key at all.

Nothing nested.

The Jira Coding Agent docs don't talk about skills themselves, so that part rests on the CLI docs.

What I'd try is a relative symlink per skill inside the root .rovodev/skills pointing at the nested folder. Untested though. Not sure the loader follows symlinks, in the CLI or the sandbox. If it doesn't, copy them to the root in a pre-commit or CI step.

All comments

Mihai_LeanZero

Nothing nested.

The Jira Coding Agent docs don't talk about skills themselves, so that part rests on the CLI docs.

Arkadiusz Wroblewski

Hello @Swati Singh

One alternative to try is adding instructions to the repository’s root AGENTS.md, which Atlassian confirms coding agents in Jira read. For example:

“When working in tests/my-project/, first read and follow tests/my-project/.rovodev/skills/<skill-name>/SKILL.md.”

This would direct the agent to your existing instructions; it wouldn’t automatically register the nested skill. I’d test it in a new session before relying on it.

Atlassian’s explanation — see question 5

Best,

Arek🤠

Swati Singh

Hey @Mihai_LeanZero ,

Thanks for the quick response and suggestion. I tried the symlink-per-skill approach and it worked. I can now see the nested skills in the Available Skills list for new sessions.

That said, a configurable skills directory would be preferable. Since I mostly work within the test project, creating symlinks for every skill in the repository root is cumbersome. I'd also prefer not to place test-specific skills in the application root to keep test assets separate from the main codebase.

Thanks again for the help!

Mihai_LeanZero

Nice, glad it picked them up.

One loop from the repo root does all of them and it's safe to rerun:

for d in tests/my-project/.rovodev/skills/*/; do ln -sfn "../../${d%/}" .rovodev/skills/; done

Committed links stay, so you only rerun it when you add a skill. Could go in a pre-commit hook with a git add .rovodev/skills after it, but hooks aren't shared on clone, so each dev installs it once. The cloud agent should get them too if its loader follows links the way your local one did.

Skills stay in the test project, only the links sit in the root. A configurable dir would still be nicer, agreed.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-cloud

rovo-agents