skills.rest
cjdutoit
cjdutoitCOMMUNITY
Explore all skills by this author →
GitHub

the-standard-practices

Standardize branch naming, commit messages, and pull request formats.

3|2|Updated Sep 19, 2024
Search Tags:#workflow#contribution#pull request#security#branch naming#commit discipline
One-click install
npx skills add https://github.com/cjdutoit/STX.EFCore.Client --skill the-standard-practices-cjdutoit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: the-standard-practices
Source: https://github.com/cjdutoit/STX.EFCore.Client/tree/main/.agents/skills/the-standard-practices
Command: npx skills add https://github.com/cjdutoit/STX.EFCore.Client --skill the-standard-practices-cjdutoit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the challenge of maintaining organized, consistent, and secure contribution processes in software projects.

Core Features & Use Cases

  • Standardized Branch Naming: Enforces naming conventions to clearly identify contributor, category, resource, and action.
  • Commit Discipline: Guides the proper use of FAIL/PASS prefixes for TDD workflow integrity.
  • Pull Request Standards: Ensures PR titles, descriptions, and review processes follow accepted formats.
  • Configuration Security: Promotes best practices for managing secrets, environment variables, and deployment settings.
  • Open Source Workflow: Reinforces forking, pull request review, and merge protocols to facilitate collaboration.

Quick Start

Use this skill to verify that all contribution and collaboration standards are followed throughout your project.

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 a consistent branch naming convention for my software team?▼

To enforce branch naming conventions, you need standardized patterns that clearly identify the contributor, category, resource, and action. This ensures organized contribution workflows and prevents naming collisions across open-source and enterprise development environments.

What should be included in pull request standards for a disciplined development workflow?▼

Pull request standards should include structured PR titles, detailed descriptions, and formal review processes. Applying these formatting rules ensures contribution workflows remain consistent and collaboration integrity is maintained across software projects.

How does commit discipline work in a TDD workflow?▼

Commit discipline in a TDD workflow requires using FAIL and PASS prefixes in commit messages to indicate test status. This maintains test-driven development integrity and enforces standardized contribution practices.

Can I use these contribution workflow standards for open-source projects?▼

Yes, these contribution workflow standards apply to open-source projects. They reinforce forking protocols, pull request reviews, and merge procedures to facilitate secure and organized collaboration.

What is the best way to manage configuration security during deployments?▼

Managing configuration security requires best practices for handling secrets, environment variables, and deployment settings. Enforcing these standards prevents accidental exposure and maintains secure contribution workflows.

Related Skills

Explore More Software Engineering Skills→
WellApp-aiWellApp-ai
341

setup

Automate one-time developer environment setup with Git, Docker, and npm.

Official
Advanced
MJ-AgentLabMJ-AgentLab

push

Push code to Gitee and GitHub after validating eight pre-push checks.

Official
Advanced
maslennikov-igmaslennikov-ig
2

code-reviewer

Automate pull-request code review across six languages with structured reports.

Community
Advanced
ByronWilliamsCPAByronWilliamsCPA

Git Workflow Skill

Enforce branch validation, commit conventions, and PR preparation in Git workflows.

Official
Basic