agentleFS
Sign inStart free
redhat-developerredhat-developer/rhdh-skills/skills/ci/rhdh-konflux-rpa/SKILL.md

rhdh-konflux-rpa

Skill20 starsChanged 22 days agoApache-2.0View on GitHub

Updates the RHDH ReleasePlanAdmission tag values in konflux-release-data for one patch release while preserving stream tags and plugin version suffixes. Use for "update the RHDH RPA tags for 1.9.7".

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Update one RHDH patch stream in a user-provided konflux-release-data checkout.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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 Konflux ReleasePlanAdmission updates

Update one RHDH patch stream in a user-provided konflux-release-data checkout. The deterministic script edits only the four hub/operator and plugin-catalog RPA files for that stream. It never commits, pushes, or opens a merge request.

Route

Load workflows/update-rpa.md and follow it end to end. Execute the bundled scripts/update_rpa_tags.py by path relative to this installed skill; do not copy its replacement logic into the conversation.

Boundaries

  • /rhdh-konflux-tasks owns Tekton task bundle digests, migrations, templates, and PipelineRun regeneration.
  • /rhdh-plugin-midstream-propagate owns a single plugin workspace and its surgical PLR tag edits.
  • This skill owns RHDH patch tags in release-data ReleasePlanAdmissions. It does not edit FBC, 1.next, 1-stage, builder RPAs, tenant snapshots, or Konflux components.

Write boundary

Inspection, --dry-run, the requested local branch, --local-only file edits, validation, and git diff stay in the user's checkout and need no write gate. The gate starts at commit: before a commit, push, or merge-request creation, invoke /mutation-gate with the exact target, command, payload preview, verification, and failure behavior for each operation. The user's request to update tags authorizes those named local edits, not publication.

The merge-request body is a fixed repository template. Fill only its named placeholders; do not invoke a runtime prose editor.

Completion

Name the old and new patch tags, every changed RPA file, validation results, the local branch and commit state, and the outcome or skipped state of the commit, push, and merge-request operations. Report explicitly when nothing was pushed.

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