skills.rest
shioki
shiokiCOMMUNITY
Explore all skills by this author →
GitHub

team-standards

Standardize team coding conventions, workflows, and review criteria.

1|Updated Jun 15, 2025
Search Tags:#onboarding#branching#guidelines#coding-standards#workflows#code-review#commit-messages
One-click install
npx skills add https://github.com/shioki/Cursor-Knowledge-Management-System --skill team-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: team-standards
Source: https://github.com/shioki/Cursor-Knowledge-Management-System/tree/main/templates/.cursor/skills/team-standards
Command: npx skills add https://github.com/shioki/Cursor-Knowledge-Management-System --skill team-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle with inconsistent coding conventions, unclear review criteria, and fragmented workflows, leading to onboarding delays and quality gaps.

Core Features & Use Cases

  • Codified coding conventions: naming rules, comment standards, and import orders to ensure uniform code across the project.
  • Unified development workflows: branch strategies, commit message guidelines, and PR criteria to streamline collaboration.
  • Onboarding and code review alignment: provides a shared standard so new members ramp up quickly and reviews stay consistent.

Quick Start

Update your repository with the team standards from this skill and begin enforcing them in code reviews and onboarding.

Frequently Asked Questions about team-standards

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

FAQPage Schema
How do I enforce team coding standards during code reviews?▼

You can enforce team coding standards during code reviews by applying codified conventions for naming, formatting, and commit messages directly to your repository. This ensures reviews stay consistent and aligns with shared project criteria.

What is the best way to reduce onboarding time for new developers?▼

Reducing onboarding time for new developers requires providing a shared standard governing development workflows and coding conventions. This helps new members ramp up quickly by removing ambiguity in day-to-day development and review expectations.

How do I standardize commit messages and branch strategies across a project?▼

Standardizing commit messages and branch strategies across a project involves implementing unified development workflows. This governs branching guidelines and PR criteria to streamline collaboration and reduce fragmented processes.

Can I use coding standards guidelines for any software engineering team?▼

These coding standards guidelines can be used by any software engineering team needing consistent conventions. They suit projects aiming to reduce quality gaps caused by unclear review criteria and fragmented workflows.

Why do we need codified conventions for import orders and naming rules?▼

Codified conventions for import orders and naming rules are needed to ensure uniform code across the project. Without them, teams struggle with inconsistent coding conventions that lead to fragmented workflows and onboarding delays.

Related Skills

Explore More Software Engineering Skills→
mcj-codermcj-coder
1

greenfield-baseline

Automate project scaffolding with quality gates, CI/CD, and repository structure.

Community
Advanced
fworks-techfworks-tech
2

the-doorman

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

Community
Advanced
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
leanEthereumleanEthereum
143

fix

Automatically fix linting and formatting issues in Python codebases.

Official
Intermediate