Skip to content

Initialize files & dirs for Agentic AI development#469

Open
stejskalleos wants to merge 1 commit intotheforeman:masterfrom
stejskalleos:ls/ai-init
Open

Initialize files & dirs for Agentic AI development#469
stejskalleos wants to merge 1 commit intotheforeman:masterfrom
stejskalleos:ls/ai-init

Conversation

@stejskalleos
Copy link
Copy Markdown
Contributor

@stejskalleos stejskalleos commented Apr 23, 2026

  • AGENTS.md
  • .agents dir with agents, skills, rules
  • settings file for Claude
  • links for Claude files

Why are you introducing these changes? (Problem description, related links)

Follow up to #457, where I introduced quite a big change for an initial commit. This is a reduced version that should build the foundation for Agentic AI development.

What are the changes introduced in this pull request?

  • AGENTS.md
  • .agents dir with agents, skills, rules
  • settings file for Claude
  • links for Claude files

How to test this pull request

Use your AI tool and observe behavior and functionality.

⚠️ Disclaimer

  • Proof of concept, I have not tested it (yet) for actual development
  • Generated with multiple AI tools (Claude, Opus 4.6 & Gemini)
  • The files & instructions should be model/tool agnostic

Comment thread .agents/rules/podman-secrets-rule.md Outdated
Comment thread .agents/settings.json.EXAMPLE
Comment thread .claude
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
@ehelms
Copy link
Copy Markdown
Member

ehelms commented Apr 23, 2026

Great start, I've been looking at https://github.com/NVIDIA/OpenShell/blob/main/AGENTS.md (and the repo) as good examples of well written and structured assets.

@stejskalleos
Copy link
Copy Markdown
Contributor Author

@ehelms applied changes as per your comments

@stejskalleos
Copy link
Copy Markdown
Contributor Author

@ehelms I'm thinking about adding a Caveman skill, what do you think?

A Claude Code skill/plugin and Codex plugin that makes agent talk like caveman — cutting ~75% of output tokens while keeping full technical accuracy. Now

@ehelms
Copy link
Copy Markdown
Member

ehelms commented Apr 24, 2026

@ehelms I'm thinking about adding a Caveman skill, what do you think?

In my experience, most of my time is reading the final outputs of agents. Having to do mental gymnastics to understand the output does not seem worth it at this point.

@ehelms
Copy link
Copy Markdown
Member

ehelms commented Apr 24, 2026

Is .agents/agents/ansible-playbook-agent.md an empty file?

Comment thread CLAUDE.md
Comment thread .agents/skills/lint-skill.md Outdated
Comment thread .agents/skills/obsah-metadata-skill.md Outdated
Comment thread .agents/skills/lint/SKILL.md Outdated
Comment thread AGENTS.md
Comment thread AGENTS.md

Features are modular capabilities that can be enabled. See [docs/developer/how-to-add-a-feature.md](docs/developer/how-to-add-a-feature.md) for the complete feature development guide.

Current features:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Features listing is something that will grow, i wonder if we should keep this updating or update it to contain Example features:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can it be an instruction to read https://github.com/theforeman/foremanctl/blob/master/src/features.yaml? Because the list is already out of date.

Comment thread .agents/skills/obsah-metadata-skill.md Outdated
@stejskalleos
Copy link
Copy Markdown
Contributor Author

Updated:

  • Fixed .agents/agents files
  • Simplified podman-secrets-rule
  • Restructured skills
  • Applied the suggestions from the comments

Comment thread .agents/agents/ansible-role-agent.md Outdated
Comment thread .agents/agents/ansible-role-agent.md Outdated
Comment thread .agents/rules/podman-secrets-rule.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md Outdated
Comment thread AGENTS.md
Comment thread .agents/skills/obsah-metadata/SKILL.md Outdated
@ehelms
Copy link
Copy Markdown
Member

ehelms commented Apr 30, 2026

I took this for a test drive implementing something. Here are my recommendations after that experience:

  1. Split out the foundational parts to a PR -- i.e. AGENTS.md
  2. The two agents are presenting more like skills rather than agents. Agents should be able to perform some autonomous action and our repository design means that splitting up how roles and playbooks interact is not a clean cut. There are often features and changes that need to touch the whole of src/. However, encapsulating how roles work, playbooks work into skills that can be used is helpful to the built in agents or future agents we might build ourselves. These skills would allow builtin agents (such as Claude's Explore and Plan agents) to use them.
  3. Let's also get in the lint skill and try it out.

@ehelms
Copy link
Copy Markdown
Member

ehelms commented May 1, 2026

Follow up, I tried implementing a feature with this PR + turning those two agents into skills and had good results. I then tried to follow up with a "testing agent" which focused on running a deploy, running tests, addressing failures. Here is the first attempt at that agent I used: #481

- AGENTS.md
- .agents dirs
- settings example file
- links for Claude files
Comment thread AGENTS.md

Flavors define the base feature set:

- `katello` - Currently the only flavor (Foreman 3.18 + Katello 4.20 + Pulp 3.85 + Candlepin 4.6)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A flavor doesn't define the versions and we've updated to always follow nightly. Perhaps leave out the versions?

Suggested change
- `katello` - Currently the only flavor (Foreman 3.18 + Katello 4.20 + Pulp 3.85 + Candlepin 4.6)
- `katello` - Currently the only flavor (Foreman + Katello + Pulp + Candlepin)

Instead of listing them, should it perhaps be instructed to read https://github.com/theforeman/foremanctl/tree/master/src/vars/flavors?

If you need a description, should we add that to a flavor? I can imagine we'll have foremanctl list-flavors or foremanctl flavor --list or some variant like that which should tell users what to select.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants