agentleFS
Sign inStart free
redhat-developerredhat-developer/rhdh-plugins/.agents/skills/rhdh-workspace/SKILL.md

rhdh-workspace

Skill51 starsChanged 2 months agoApache-2.0View on GitHub

Route work in the rhdh-plugins monorepo to the affected workspace and package. Use before doing any work under workspaces/, including documentation-only changes.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before running Yarn commands, install dependencies from the workspace root with YARN_ENABLE_SCRIPTS=false yarn install --immutable.

    line 17
  2. Distinctive:

    Run build, lint, fix, API-report, and dedupe commands from the workspace root.

    line 20
  3. Distinctive:

    Run tests from the affected package directory or with an explicit package filter.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

RHDH Workspace

Identify the affected workspaces/<name> from changed files or its workspace/<name> issue label. Change to that workspace and read its AGENTS.md, if present — it contains coding conventions, documentation conventions, and testing requirements that apply to all changes in the workspace.

Before running Yarn commands, install dependencies from the workspace root with YARN_ENABLE_SCRIPTS=false yarn install --immutable.

Run build, lint, fix, API-report, and dedupe commands from the workspace root. Run tests from the affected package directory or with an explicit package filter. Do not run unfiltered workspace-wide tests; they exceed the Fullsend sandbox timeout.

Before finishing

These CI gates apply across workspaces. Run them from the workspace root and commit any generated files.

  • API reports — if public exports or function signatures changed, run yarn build:api-reports:only --ci (and yarn fix if package metadata moved).
  • Type check — if TypeScript files were added or modified, run yarn tsc in the workspace root. CI runs yarn tsc:full (non-incremental) and will reject type errors that unit tests miss (JavaScript ignores argument count mismatches that TypeScript catches).
  • Prettier — run yarn prettier:check (or yarn prettier:fix when that script exists).
  • Dedupe — if the lockfile changed, run yarn dedupe.
  • Changesets — for user-facing changes to published packages, add a .changeset/ entry. Check the workspace AGENTS.md for when a changeset is required vs skippable.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free