The Standard Practices

Enforce standardized contribution workflows, branch naming, and PR reviews.

1|Updated Sep 25, 2025

Search Tags:#git #tdd #branching #governance #pull-request #standard #commit-discipline

Ready to run

npx skills add https://github.com/NHSISL/LondonFhirService --skill the-standard-practices

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: The Standard Practices
Source: https://github.com/NHSISL/LondonFhirService/tree/main/.agents/skills/the-standard-practices
Command: npx skills add https://github.com/NHSISL/LondonFhirService --skill the-standard-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces a standardized, governance-focused approach to contribution workflows, branching conventions, and review processes across software projects.

Core Features & Use Cases

Standard contribution workflow from fork to PR, including branch naming conventions, configuration guidance, and measurement practices
Consistent branch naming, category discipline, and category-based PR/ticket alignment to improve traceability and fairness
TDD discipline guidance, review templates, and governance mechanisms to support quality and growth
Guidance on environment, secrets handling, and secure configuration to reduce risk and leakage
Templates, contracts, and checks to align PRs, commits, and releases with the Standard

Quick Start

Plan work using the standard practices, name branches according to the canonical pattern, and open PRs following the Standard format.

Frequently Asked Questions about The Standard Practices

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

FAQPage Schema

How do I enforce git branch naming conventions and commit discipline across my team?▼

To enforce git branch naming and commit discipline, you apply rule-based checks and templates loaded via a standard core. This standardizes branch naming, commit messages, and PR titles to align contributions with governance policies.

What is the best way to standardize pull request templates and reviews?▼

Standardizing pull request reviews involves applying governance mechanisms and review templates to guide PR titles and category alignment. This ensures consistent PR reviews and aligns releases with standard practices.

Does TDD discipline guidance work with standard branching and PR workflows?▼

Yes, TDD discipline guidance integrates with standard branching and PR workflows. It provides review templates and governance mechanisms to support quality and growth alongside standardized branch naming and contribution cycles.

How do I handle secrets and secure configuration during pull request governance?▼

Handling secrets and secure configuration during PR governance requires guidance on environment management and configuration safety. This reduces risk and prevents leakage by applying standard checks to configuration changes.

Can I apply governance checks across infrastructure, data, and service layers?▼

Yes, you can apply governance checks across infrastructure, data, brokers, and service layers. This standardizes naming, auditing, and planning during commits and PR cycles to enforce a consistent contribution workflow.

When should I use a standard-driven workflow for contributions and PR reviews?▼

You should use a standard-driven workflow when you need to enforce consistent naming, auditing, and planning across multiple layers. It is essential for improving traceability, fairness, and configuration safety in team environments.