agentleFS
Sign inStart free
redhat-developerredhat-developer/rhdh-users-skill-pack/AGENTS.md

rhdh-users-skill-pack

AGENTS.md1 starsChanged 10 days agoApache-2.0View on GitHub

RHDH Users Agent Plugin — Agent Skills for Red Hat Developer Hub (RHDH) users, packaged as an Agent Plugin (plugin.json at the repository root). Skills follow the Agent Skills open standard. Don't assume. Don't hide confusion. Surface tradeoffs. Before implementing: Minimum code that solves the problem. Nothing speculative. Bundled Python scripts should prefer the standard library. Avoid new runtime dependencies unless clearly justified. Touch only what you must. Clean up only your own mess. When editing existing code: When your…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. redhat-developer/rhdh-users-agent-plugin★ 1100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,843 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository4 other files it gives its agents.

The file

Show its rules and text

We split this AGENTS.md into the rules it gives an agent

17 rules. About 0 are common, 13 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    If multiple interpretations exist, present them — don't pick silently.

    line 12
  2. Distinctive:

    If a simpler approach exists, say so.

    line 13
  3. Distinctive:

    If something is unclear, stop.

    line 14
  4. Distinctive:

    No features beyond what was asked.

    line 20
  5. Distinctive:

    No abstractions for single-use code.

    line 21
  6. Distinctive:

    If you write 200 lines and it could be 50, rewrite it.

    line 23
  7. Distinctive:

    When editing existing code:

    line 31
  8. Distinctive:

    Don't "improve" adjacent code, comments, or formatting.

    line 33
  9. Distinctive:

    Don't refactor things that aren't broken.

    line 34
  10. Distinctive:

    If you notice unrelated dead code, mention it — don't delete it.

    line 36
  11. Distinctive:

    When your changes create orphans:

    line 38
  12. Very specific:

    Remove imports/variables/functions that YOUR changes made unused.

    line 40
  13. Distinctive:

    Don't remove pre-existing dead code unless asked.

    line 41
  14. Very specific:

    Run uv run pytest before reporting any task complete.

    line 55
  15. Distinctive:

    Never force push, reset HEAD, merge branches, or run destructive commands without asking.

    line 59
  16. Very specific:

    If told an implementation was wrong, apply the correction and then record what went wrong so the same mistake is not repeated.

    line 63
  17. Very specific:

    When adding a skill, update README.md and keep SKILL.md name aligned with the directory name per the Agent Skills spec.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md

AGENTS.md

RHDH Users Agent Plugin — Agent Skills for Red Hat Developer Hub (RHDH) users, packaged as an Agent Plugin (plugin.json at the repository root). Skills follow the Agent Skills open standard.

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

Before implementing:

  • State your assumptions explicitly. If uncertain, ask.
  • If multiple interpretations exist, present them — don't pick silently.
  • If a simpler approach exists, say so. Push back when warranted.
  • If something is unclear, stop. Name what's confusing. Ask.

2. Simplicity First

Minimum code that solves the problem. Nothing speculative.

  • No features beyond what was asked.
  • No abstractions for single-use code.
  • No "flexibility" or "configurability" that wasn't requested.
  • If you write 200 lines and it could be 50, rewrite it.

Bundled Python scripts should prefer the standard library. Avoid new runtime dependencies unless clearly justified.

3. Surgical Changes

Touch only what you must. Clean up only your own mess.

When editing existing code:

  • Don't "improve" adjacent code, comments, or formatting.
  • Don't refactor things that aren't broken.
  • Match existing style, even if you'd do it differently.
  • If you notice unrelated dead code, mention it — don't delete it.

When your changes create orphans:

  • Remove imports/variables/functions that YOUR changes made unused.
  • Don't remove pre-existing dead code unless asked.

The test: every changed line should trace directly to what was asked.

4. Goal-Driven Execution

Define success criteria. Loop until verified.

Transform tasks into verifiable goals:

  • "Add validation" → "Write tests for invalid inputs, then make them pass"
  • "Fix the bug" → "Write a test that reproduces it, then make it pass"
  • "Refactor X" → "Ensure tests pass before and after"

Run uv run pytest before reporting any task complete. Do not report completion based on code existing — verify it works.

5. No Irreversible Commands Without Confirmation

Never force push, reset HEAD, merge branches, or run destructive commands without asking. If unsure whether a command is destructive, ask.

6. Learn From Corrections

If told an implementation was wrong, apply the correction and then record what went wrong so the same mistake is not repeated. Patterns and gotchas specific to this project belong in the relevant references/ file under each skill.

Available skills

User-facing skills live under skills/:

  • rhdh-templates — Software Templates authoring and validation
  • skill-maker — Create, audit, and consolidate Agent Skills
  • rhdh-upgrade-helper — Upgrade assessment for RHDH — analyzes config files against a target release to produce a prioritized migration plan with readiness scoring

When adding a skill, update README.md and keep SKILL.md name aligned with the directory name per the Agent Skills spec. Do not nest a plugin.json inside a skill directory; the Plugin manifest stays at the repository root.

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