CI Sentinel

Name: CI Sentinel
Availability: InStock
Author: ninaverde

Enforce Conventional Commits standards for PR titles and commit messages in Flutter GitHub workflows.

Updated Aug 11, 2025

Search Tags:#automation #github-actions #ci-cd #flutter #commit-message #conventional-commits #pr-title

Ready to run

npx skills add https://github.com/NinaVerde/ninaverde_app --skill ci-sentinel

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: CI Sentinel
Source: https://github.com/NinaVerde/ninaverde_app/tree/main/.agent/skills/ci-sentinel
Command: npx skills add https://github.com/NinaVerde/ninaverde_app --skill ci-sentinel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures GitHub PR titles and commit messages follow Conventional Commits standards and protects Flutter projects with enforced CI checks.

Core Features & Use Cases

Enforces PR title formats and conventional commit types via amannn/action-semantic-pull-request.
Validates Flutter CI workflow configuration to maintain consistent quality gates across PRs.
Use Case: Teams leveraging Flutter on GitHub can auto-check PR titles, commit messages, and CI readiness before merging.

Quick Start

Add or review your GitHub Actions workflows to include the semantic PR check and ensure the repository uses conventional commits. Then, before creating a PR, craft your commits and PR titles to match the defined types (feat, fix, chore, docs, refactor, test, ci) and the subject format.

Frequently Asked Questions about CI Sentinel

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

FAQPage Schema

How do I enforce conventional commit PR titles in GitHub Actions for a Flutter project?▼

To enforce conventional commit PR titles in GitHub Actions, configure the amannn/action-semantic-pull-request workflow to validate PR titles against allowed types like feat, fix, and chore before merging Flutter repository pull requests.

What conventional commit types are allowed for GitHub PR titles and commit messages?▼

The allowed conventional commit types for PR titles and commit messages are feat, fix, chore, docs, refactor, test, and ci. Your PR subject formatting must match these defined types to pass the GitHub Actions quality gate checks.

Does this Skill require specific GitHub Actions configurations to run Flutter CI checks?▼

Yes, it requires an existing Flutter CI workflow and the action-semantic-pull-request configuration in your GitHub repository. These enforce allowed commit types and subject formatting while validating CI readiness across PRs.

How do I validate Flutter CI workflow configuration before creating a pull request?▼

To validate your Flutter CI workflow configuration, ensure your GitHub Actions workflows include the semantic PR check and Flutter CI gates. Craft your commits and PR titles to match defined conventional types before creating a PR.

Why does my PR title fail the semantic pull request check in GitHub Actions?▼

Your PR title fails the semantic pull request check when it does not match the enforced conventional commit types or subject formatting. Ensure your titles use allowed prefixes like feat, fix, or docs to pass the CI gate.