mcpbeat

Iri Mcd

openshift/iri-mcd

Describes the acceptance criteria and BDD tests to be used for new/existing features of the InternalReleaseImage MachineConfigDaemon manager. The manager implements the NoRegistryClusterInstall main feature for the part related to manage/monitor a single control plane node

1k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
0
copies elsewhere
how many repositories repackaged it
267
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/openshift/machine-config-operator --skill iri-mcd

What comes with it

1 833 bytes besides the instruction
acceptance/feature-disabled.md
acceptance/storage-reclaim.md

The instruction itself

6 sections, as written by the author

InternalReleaseImage daemon manager BDD workflow

When working on InternalReleaseImage daemon manager changes:

  • Identify the specific behavior being changed.
  • Read only the relevant acceptance file under acceptance/.
  • If the change touches multiple behaviors, read all matching files.
  • Do not invent behavior that is not covered by the acceptance criteria.
  • When behavior changes, update the relevant acceptance file before implementing code.

General implementation notes

When defining the implementation:

  • Ensure that any new portion of code is covered at least by one or more unit tests.
  • Keep production changes minimal.
  • Avoid duplications, prefer a coding style that improves the readability and maintenance.
  • Do not perform broad refactors unless needed to make the behavior testable.
  • If a behavior is not covered by acceptance criteria, stop and ask before implementing it.
  • When reporting completion, map each changed test back to the acceptance scenario it covers.
  • Minimize comments, and keep them short.

Specific IRI MCD manager implementation notes

  • Keep the syncInternalReleaseImage method short and readable. Prefer to refactor included tasks into private type methods.
  • Do not instantiate the IRI registry within syncInternalReleaseImage method more than once per loop: keep it simple stupid.

Test implementation notes

  • When testing different cases for the same scenario, use the cases := []struct{} to capture the relevant key fields for the test. Add always a speaking

name field to represent the current case.

  • Reuse the existing test methods if possible.
  • Keep the test focused on the behaviors, avoid testing unnecessary technical details.
  • Do not add too many comments to the tests

Functional testing notes

The NoRegistryClusterInstall feature is also tested functionally in /test/e2e-iri folder.

Supporting files

  • acceptance/storage-reclaim.md: IRI deletion workflow, how to reclaim the disk node space previously used.
  • acceptance/feature-disabled.md: the expected behavior when the feature is not enabled.

How to use it

Copy the folder

Take openshift/iri-mcd from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.