collection-review

Automate Ansible collection pull request reviews for STIG compliance.

Updated Apr 10, 2026

Search Tags:#automation #code review #compliance #ansible #network security #stig

Ready to run

npx skills add https://github.com/redhat-cop/network.compliance --skill collection-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: collection-review
Source: https://github.com/redhat-cop/network.compliance/tree/main/.agents/skills/collection-review
Command: npx skills add https://github.com/redhat-cop/network.compliance --skill collection-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, ansible-lint, tox.

What problem does it solve?

This Skill addresses the challenge of maintaining high-quality, production-ready Ansible Validated Content by providing a structured framework for reviewing pull requests against strict STIG compliance and coding standards.

Core Features & Use Cases

STIG Rule Validation: Cross-references new STIG rule implementations against authoritative DISA source data to ensure accuracy.
Standard Enforcement: Validates code against Ansible Validated Content requirements, including FQCN usage, task naming conventions, and security best practices like no_log.
Use Case: When a developer submits a PR adding a new Cisco IOS STIG rule, use this Skill to verify that the task names, tags, and remediation logic align with the collection's strict architectural and security requirements.

Quick Start

Use the collection-review skill to audit the pull request number 123 for compliance with STIG and Ansible standards.

Frequently Asked Questions about collection-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate STIG compliance checks for Ansible collection pull requests?▼

Automate STIG compliance checks for Ansible pull requests by cross-referencing new rule implementations against DISA source data and validating code against security best practices. It applies structured technical reviews to enforce production-ready standards.

What is Ansible Validated Content enforcement for network security configurations?▼

Ansible Validated Content enforcement is the process of verifying code against strict architectural requirements, including FQCN usage, task naming conventions, and security practices like no_log. It ensures network device configurations meet compliance standards.

Do I need the GitHub CLI to review Ansible code for DISA STIG guidelines?▼

Yes, you need the GitHub CLI to review Ansible code for DISA STIG guidelines, along with ansible-lint and tox. These dependencies are required to execute quality checks and verify adherence to validated content standards.

How do I validate Cisco IOS STIG rules in an automated testing scenario?▼

Validate Cisco IOS STIG rules by auditing the pull request to verify task names, tags, and remediation logic align with strict architectural and security requirements. This ensures accuracy against authoritative DISA source data in automated testing scenarios.

What's the best way to enforce no_log and FQCN usage in Ansible collections?▼

Enforce no_log and FQCN usage by applying an automated technical review framework that validates code against Ansible Validated Content requirements. This cross-references implementations to ensure coding standards and security best practices are met.

Why does my ansible-lint validation fail during STIG rule implementation?▼

Ansible-lint validation fails during STIG rule implementation when code does not adhere to Ansible Validated Content requirements, such as missing FQCN usage, incorrect task naming conventions, or lacking security practices like no_log. The skill identifies these specific architectural misalignments.