Agents & OrchestrationSûr100100/100

review ansible ansible

Review an Ansible PR following the project's standardized process from CLAUDE.md

ou envoie-le directement à ton agent.

Installer dans ton projet

$ npx arboris-cli install review__ansible-ansible__claude-skills-9734495d581c

Contenu à copier

---
name: review
description: Review an Ansible PR following the project's standardized process from CLAUDE.md
argument-hint: <pr_number>
allowed-tools: [TodoWrite, Bash(gh pr view:*), Bash(gh pr diff:*), Bash(gh pr checkout:*), Bash(gh pr checks:*), Read, Grep, Glob, Search]
user-invocable: true
metadata:
  origin: Ansible
---

PR Review Command
=================

Review an Ansible PR following the project's standardized process from `CLAUDE.md`.

Usage
-----

```bash
/review <pr_number>
```

Arguments
---------

- `pr_number` (required): The GitHub PR number to review

Implementation
--------------

This command implements the PR Review Guidelines documented in the `PR Review Guidelines` section of CLAUDE.md.

Review Process Steps
--------------------

The command follows these numbered steps from CLAUDE.md:

1. **Create TodoWrite list** for systematic review tracking
2. **Get PR details**: `gh pr view <number>` to understand scope, motivation and the desired outcome
3. **Get PR diff**: `gh pr diff <number>` to see all changes
4. **Check required components FIRST**:
   - Verify changelog fragment exists in `changelogs/fragments/`
   - Verify changelog uses correct section (check `changelogs/config.yaml`)
   - Verify tests exist and specifically cover the changed code paths
   - Unit tests should be pytest style, and functional rather than tightly coupled to mocking
   - Integration tests required for almost all plugin changes
5. **Checkout PR branch**: `gh pr checkout <number>` to examine code holistically
6. **Review existing feedback**: `gh pr view <number> --comments` for all comments and previous reviews
7. **Verify all issues addressed**: Ensure bot failures, reviewer requests, and discussion points are resolved
8. **Call out unresolved feedback**: Explicitly mention any discussions/requests that remain unaddressed

Critical Review Elements
------------------------

- **Licensing**: Verify GPLv3/BSD-2-Clause compatibility for any new dependencies
- **Test scope**: Tests must exercise actual changed code, not just add random coverage
- **Changelog validation**: Fragment structure follows sections defined in `changelogs/config.yaml`

Each step is tracked in TodoWrite for visibility and systematic completion. A review round should not exceed 20 feedback items.

Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.

Ce que fait review ansible ansible

`pr_number` (required): The GitHub PR number to review

Verify changelog fragment exists in `changelogs/fragments/`

Verify changelog uses correct section (check `changelogs/config.yaml`)

Verify tests exist and specifically cover the changed code paths

Comment utiliser review ansible ansible

Copie le prompt

Un clic copie le prompt packagé (ou l'envoie à ton agent).

L'agent installe le skill

Il ajoute le SKILL.md et ses ressources à ton projet.

Activation automatique

Le skill s'active dès que le contexte correspond.

Déclencheurs pour review ansible ansible

Dis simplement à ton agent quelque chose comme :

Applique le skill review__ansible-ansible__claude-skills-9734495d581c à cette tâche

Utilise review__ansible-ansible__claude-skills-9734495d581c pour améliorer cette implémentation

Passe en revue ce sujet avec review__ansible-ansible__claude-skills-9734495d581c

Skills liés à review ansible ansible

acceleration microsoft aibast agents library

Compare synthetic acceleration options and clearly separate scenario value from forecast commitments.

account overview microsoft aibast agents library

Create a synthetic Acme account overview and identify evidence that merits seller attention.

acroform writer microsoft cat agent skills

Use this skill whenever the user wants values written INTO an existing PDF form that lives in the connected SharePoint knowledge source — filling out, completing, populating, or submitting a fillable PDF (application, intake sheet, contract, government form) from data they supply, a spreadsheet row, or the conversation. Triggers include "fill out the job application form", "complete the intake form for [person]", "populate our standard NDA template", and "make this ready to send / non-editable" (flatten). The source form should be found via knowledge search; only ask the user to upload it if knowledge search turns up nothing plausible. different task), and do NOT use it on scanned/image-only PDFs that have no real fillable fields — those need OCR or manual overlay instead, which this skill explicitly detects and reports rather than silently failing.