ci: Skip reviews for PRs with [citest_skip] in the title

[spetrosi]

• Add info about .coderabbit.yam for AI assistants to contributing.md
• Note that CodeRabbit uses config from the main branch so this change will apply
  after this PR is merged.

[coderabbitai]

📝 Walkthrough

Walkthrough

This pull request establishes repository-wide AI coding standards and updates dependency versioning. A new CodeRabbit configuration enforces Ansible best practices including idempotency, check-mode support, and testing requirements, while the contributing guide documents these standards. Additionally, the Ansible collection dependency specification is updated to pin the ansible.posix collection version.

Changes

CodeRabbit AI Coding Standards

Layer / File(s)	Summary
CodeRabbit configuration and documentation .coderabbit.yaml, contributing.md	A comprehensive .coderabbit.yaml file disables non-essential CodeRabbit features (poem, fortune, auto-assign) and defines path-based instruction rules for Ansible roles, handlers, templates, variables, Python code, and README documentation. The contributing guide documents that this file establishes coding standards for AI-generated code.

Ansible Collection Dependency Versioning

Layer / File(s)	Summary
ansible.posix collection version constraint meta/collection-requirements.yml	The ansible.posix collection dependency is pinned to version range >=2.1.0,<2.2.0.

🚥 Pre-merge checks | ✅ 3 | ❌ 3

❌ Failed checks (3 warnings)

Check name	Status	Explanation	Resolution
Description Format	⚠️ Warning	PR description does not follow the required template structure from .github/pull_request_template.md. Missing mandatory "Enhancement:"/"Feature:", "Reason:", and "Result:" sections.	Reformat PR description to include Enhancement/Feature, Reason, Result, and optional Issue Tracker Tickets sections as specified in the template.
Title check	⚠️ Warning	The PR title does not follow Conventional Commits format; it lacks a proper type prefix and describes CI review-skipping behavior rather than the main changes (adding CodeRabbit configuration and documentation).	Change title to follow Conventional Commits format (e.g., 'ci: Add CodeRabbit configuration' or 'chore: Configure CodeRabbit with custom rules and CI behavior').
Description check	⚠️ Warning	The PR description is largely incomplete; it lacks all required template sections (Enhancement, Reason, Result, Issue Tracker Tickets) and only provides bullet-point notes.	Fill in the template sections with detailed information: Enhancement (what was added), Reason (why), Result (expected outcome), and Issue Tracker Tickets (if applicable).

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

meta/collection-requirements.yml (1)

1-1: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Don’t directly edit meta/collection-requirements.yml; update the linux-system-roles/.github source instead
meta/collection-requirements.yml is marked “DO NOT EDIT…managed by linux-system-roles/.github”, and .coderabbit.yaml states the file is managed from that repo (manual edits will be overwritten). This change should come from the upstream managed source.
The ansible.posix constraint >=2.1.0,<2.2.0 is valid for allowing only 2.1.x, and upstream ansible.posix reports no published security advisories.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@meta/collection-requirements.yml` at line 1, The change was made directly in
the managed requirements file instead of the upstream source; revert edits to
meta/collection-requirements.yml and instead update the managed source in
linux-system-roles/.github so the constraint remains authored upstream, leaving
the ansible.posix constraint string ">=2.1.0,<2.2.0" intact; also ensure
.coderabbit.yaml still declares that this file is managed upstream to prevent
future manual edits.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@meta/collection-requirements.yml`:
- Line 1: The change was made directly in the managed requirements file instead
of the upstream source; revert edits to meta/collection-requirements.yml and
instead update the managed source in linux-system-roles/.github so the
constraint remains authored upstream, leaving the ansible.posix constraint
string ">=2.1.0,<2.2.0" intact; also ensure .coderabbit.yaml still declares that
this file is managed upstream to prevent future manual edits.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: a1b67c02-a456-4f49-bd74-e03a0306e741

📥 Commits

Reviewing files that changed from the base of the PR and between 62b8461 and bd9c38f.

📒 Files selected for processing (3)

• .coderabbit.yaml
• contributing.md
• meta/collection-requirements.yml