Template

Files

lmiranda 2d51df7a42 feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]

Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action>
sub-command pattern. Git-flow consolidated from 8→5 commands (commit
variants absorbed into --push/--merge/--sync flags). Dispatch files,
name: frontmatter, and cross-reference updates for all plugins.

Phase 2: Design documents for 8 new plugins in docs/designs/.

Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate,
saas-react-platform, saas-test-pilot, data-seed, ops-release-manager,
ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents,
skills, README, and claude-md-integration. Marketplace grows from 12→20.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-06 14:52:11 -05:00

2.5 KiB

Raw Blame History

name, description

name	description
repo-validation	Repository organization check and label taxonomy validation

Repository Validation

Purpose

Validates that the repository belongs to an organization and has the required label taxonomy.

When to Use

Planner agent: At start of sprint planning
Commands: /sprint plan, /labels sync, /pr init

Step 1: Detect Repository from Git Remote

git remote get-url origin

Parse output to extract owner/repo:

SSH: git@host:owner/repo.git → owner/repo
SSH with port: ssh://git@host:port/owner/repo.git → owner/repo
HTTPS: https://host/owner/repo.git → owner/repo

Step 2: Validate Organization Ownership

validate_repo_org(repo="owner/repo")

If NOT an organization repository:

REPOSITORY VALIDATION FAILED

This plugin requires the repository to belong to an organization, not a user.
Current repository appears to be a personal repository.

Please:
1. Create an organization in Gitea
2. Transfer or create the repository under that organization
3. Update your configuration

Step 3: Validate Label Taxonomy

get_labels(repo="owner/repo")

Required label categories:

Category	Required Labels
Type/*	Bug, Feature, Refactor, Documentation, Test, Chore
Priority/*	Low, Medium, High, Critical
Complexity/*	Simple, Medium, Complex
Efforts/*	XS, S, M, L, XL

If labels are missing:

Use create_label_smart() to create them (auto-detects org vs repo level)
Report which labels were created

Validation Report Format

Repository Validation
=====================

Git Remote: git@gitea.example.com:org/repo.git
Detected: org/repo

Organization Check:
  ✓ Repository belongs to organization "org"

Label Taxonomy:
  ✓ Type/* labels: 6/6 present
  ✓ Priority/* labels: 4/4 present
  ✓ Complexity/* labels: 3/3 present
  ✓ Efforts/* labels: 5/5 present

All validations passed. Ready for planning.

Error Handling

Repository Not Found (404)

Repository validation failed: Not found

The repository "owner/repo" does not exist or you don't have access.
Please verify:
1. Repository name is correct
2. Your token has repository access
3. Organization/owner name is correct

Authentication Error (401/403)

Repository validation failed: Authentication error

Your Gitea token may be invalid or lack permissions.
Please verify:
1. Token is valid and not expired
2. Token has 'repo' scope
3. You have access to this repository

2.5 KiB Raw Blame History