the-doorman

Validate commit messages, PR titles, and branch health with commitlint and Husky.

2|Updated May 23, 2026
One-click install
npx skills add https://github.com/fworks-tech/agenthood --skill the-doorman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: the-doorman
Source: https://github.com/fworks-tech/agenthood/tree/main/members/the-doorman
Command: npx skills add https://github.com/fworks-tech/agenthood --skill the-doorman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates commit messages, PR titles, and repository health to enforce consistent standards and protect main branches from unsafe changes.

Core Features & Use Cases

  • Local commit-msg validation using commitlint on every commit
  • CI-based PR title validation and branch protection checks
  • Health checks for repository hygiene and main-branch guardrails
  • On-demand health audits and policy enforcement for new projects

Quick Start

Run the Doorman health check to audit repository hygiene and enforce conventions.

Frequently Asked Questions about the-doorman

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

FAQPage Schema
How do I enforce commit message conventions using commitlint?

Commitlint enforces commit message conventions by validating commit messages locally via Husky hooks and in CI pipelines. This ensures consistent repository history and prevents non-compliant commits from entering the main branch.

What is the best way to validate PR titles in CI pipelines?

Validating PR titles in CI pipelines involves running automated checks that enforce repository conventions on every pull request. This prevents unsafe changes from merging into the main branch by blocking non-compliant titles during CI health checks.

How do I set up branch protection rules to secure my main branch?

Branch protection rules secure your main branch by enforcing CI health checks and PR validation before merging. Configuring these guardrails prevents direct pushes and ensures all changes pass commit and PR title conventions.

Can I use Husky hooks to validate commits locally before pushing?

Yes, Husky hooks validate commits locally before pushing by running commitlint checks on every commit. This applies repository conventions directly on the developer machine, stopping invalid commit messages early.

How do I run a repository health check to audit branch protection and hygiene?

Running a repository health check audits branch protection and hygiene by evaluating main-branch guardrails and convention enforcement. This on-demand audit identifies missing CI validations, Husky hook configurations, and branch protection gaps.

Does commit validation work with existing CI workflows without extra dependencies?

Commit validation integrates with existing CI workflows without extra dependencies by applying commitlint and PR title checks directly in the pipeline. It evaluates repository health and enforces conventions without requiring additional component installations.