repo-validation

Validate Git repository organization ownership and required label taxonomy.

Updated Jan 26, 2026
One-click install
npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill repo-validation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-validation
Source: https://github.com/l3ocho/mktpl-claude-datasaas/tree/main/plugins/projman/skills/repo-validation
Command: npx skills add https://github.com/l3ocho/mktpl-claude-datasaas --skill repo-validation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates that a repository belongs to an organization and enforces a standard label taxonomy to support consistent planning and governance.

Core Features & Use Cases

  • Organization ownership check: Determine if the repository is owned by an organization rather than a personal account.
  • Label taxonomy validation: Ensure required label categories (Type/, Priority/, Complexity/, Efforts/) exist and are applied.
  • Remediation guidance: Provide actionable steps to transfer ownership and create missing labels to meet governance standards.
  • Sprint planning readiness: Ensure repositories involved in planning have validated ownership and labeling before execution.

Quick Start

Run the repository validation command to verify organization ownership and label taxonomy.

Frequently Asked Questions about repo-validation

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

FAQPage Schema
How do I check if a Git repository belongs to an organization?

To check if a Git repository belongs to an organization, validate the repository ownership to determine if it is owned by an organization rather than a personal account, ensuring it meets governance standards for sprint planning.

What is the standard label taxonomy for sprint planning readiness?

Standard label taxonomy for sprint planning readiness requires repositories to have specific label categories, ensuring Type, Priority, Complexity, and Efforts labels exist and are properly applied for consistent planning.

How do I enforce required labels like Type, Priority, Complexity, and Efforts on Gitea repositories?

To enforce required labels like Type, Priority, Complexity, and Efforts on Gitea repositories, run a label taxonomy validation process that checks for missing categories and handles automatic label creation as needed.

Does repo validation provide remediation steps for missing labels and ownership?

Yes, repo validation provides remediation guidance for missing labels and ownership by reporting actionable steps to transfer repository ownership and create missing labels to meet governance standards.

When do I need to validate repository ownership and label taxonomy?

You need to validate repository ownership and label taxonomy during sprint planning and label synchronization to ensure repositories involved in execution have validated ownership and correct labeling before proceeding.