One-click install
npx skills add https://github.com/guardiatechnology/design-system --skill kata-contribute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kata-contribute
Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-contribute
Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-contribute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps contributors consistently create a correct pull request by validating commit history, using a proper branch workflow, and filling the repository PR template so changes are reviewable and traceable.

Core Features & Use Cases

  • Conventional and Lexis compliance: checks that commits match the required Lexis conventions before proposing a PR.
  • Branch-safe PR flow: ensures the PR is created from a non-main branch and follows a name convention inferred from commit scope.
  • Template-driven PR creation via MCP: reads the PR template (when present), composes an English Conventional Commits title, and creates the PR using MCP with the correct target branch.

Use Case: You made a set of commits on a feature/fix/docs change and want an MCP-assisted workflow that verifies the commit standards, pushes your branch, and opens a properly formatted PR against main.

Quick Start

Ask an AI to run the kata-contribute workflow to create your pull request in the origin repository via MCP using your current commits.

Frequently Asked Questions about kata-contribute

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

FAQPage Schema
How do I create a pull request with conventional commits using MCP?

To create a pull request with conventional commits using MCP, you need a workflow that validates your commit history against Lexis rules, generates an English Conventional Commits title, and calls MCP pull_request_create with the correct organization and repository parameters.

How do I automate branch validation before opening a GitHub PR?

Automating branch validation before opening a GitHub PR involves checking that commits are pushed from a non-main branch and inferring the branch name from the commit scope to ensure a safe PR creation flow against main.

How do I populate a GitHub PR template automatically when creating a PR?

To populate a GitHub PR template automatically, the PR creation process reads the .github/pull_request_template.md file when available and uses that content to compose the PR body before opening the pull request.

What is the safe way to open a pull request against the main branch?

The safe way to open a pull request against main requires branching validation to ensure you are not working directly on main, enforcing Conventional Commits compliance, and using MCP to create the PR with correct target parameters.

Does PR creation automation work without a pull request template file?

Yes, PR creation automation works without a template file, but it relies on .github/pull_request_template.md only when available to populate the PR body, meaning it will proceed with PR creation even if the template is missing.