dangerfile

Enforces configurable Danger rules and CI environment variables on GitHub pull requests via automated checks.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/messeb/skills --skill dangerfile
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dangerfile
Source: https://github.com/messeb/skills/tree/main/plugins/general-developer/skills/dangerfile
Command: npx skills add https://github.com/messeb/skills --skill dangerfile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the enforcement of team conventions and best practices within pull requests, reducing manual review effort and ensuring consistency.

Core Features & Use Cases

  • Automated Checks: Enforces rules for PR descriptions, size, test coverage, and sensitive file changes.
  • CI Integration: Integrates seamlessly with CI/CD pipelines to provide immediate feedback on pull requests.
  • Use Case: Automatically flag pull requests that modify source code without corresponding test changes, or that accidentally commit sensitive information like API keys.

Quick Start

Use the dangerfile skill to audit the current pull request for common issues.

Frequently Asked Questions about dangerfile

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

FAQPage Schema
How do I automate code review checks in GitHub Actions pull requests?

Automate code review checks in GitHub Actions by configuring Danger rules to enforce PR conventions, test coverage, and sensitive file protections. This skill audits pull requests automatically within your continuous integration workflows to provide immediate feedback.

What kind of PR automation can I enforce for team conventions and best practices?

PR automation for team conventions can enforce rules for pull request descriptions, PR size, test coverage, and sensitive file changes. It automatically flags pull requests that modify source code without corresponding test changes or accidentally commit API keys.

How do I integrate Dangerfile checks into my CI pipeline?

Integrate Dangerfile checks into CI pipelines by applying automated rules during continuous integration runs. This requires configuring Danger rules and setting CI environment variables for GitHub token access to enable automated checks on pull requests.

Can I use this to prevent committing sensitive information in pull requests?

You can prevent committing sensitive information in pull requests by applying automated Danger checks. This skill flags pull requests that accidentally commit sensitive data like API keys, enforcing team conventions before changes are merged.

Do I need specific environment variables to run Danger rules in GitHub Actions?

Running Danger rules in GitHub Actions requires configuring CI environment variables for GitHub token access. This environment setup allows the automated code review checks to interact with pull requests and post feedback.

What is the best way to enforce test coverage requirements on modified source code?

The best way to enforce test coverage requirements is using automated PR checks that flag pull requests modifying source code without corresponding test changes. This ensures consistency and reduces manual review effort across the team.