make-repo-contribution

Enforce repository contribution guidelines across issues, branches, commits, and pull requests.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/shysssthanhtri/AI-tools --skill make-repo-contribution-shysssthanhtri
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: make-repo-contribution
Source: https://github.com/shysssthanhtri/AI-tools/tree/main/skills/make-repo-contribution
Command: npx skills add https://github.com/shysssthanhtri/AI-tools --skill make-repo-contribution-shysssthanhtri

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces and standardizes how contributors create issues, branches, commits, and PRs to follow the repository's governance rules and templates.

Core Features & Use Cases

  • Guided contribution workflow: Provides a clear process from issue creation through PR submission, including branch naming and commit message conventions.
  • Safety and compliance: Upholds security boundaries, templates, and validation steps to reduce missteps and non-compliant changes.
  • Template-driven collaboration: Encourages use of standardized issue/PR templates to capture necessary information and maintain consistency.

Quick Start

Review and apply the repository's contribution guidelines before creating any issue, branch, commit, or PR.

Frequently Asked Questions about make-repo-contribution

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

FAQPage Schema
How do I standardize pull request and commit message conventions for repository contributions?

Standardize repository contributions by applying enforced governance rules across issue creation, branch naming, commit messages, and pull request templates before acting. This ensures compliant changes and reduces missteps during collaboration.

What is the best way to enforce contribution guidelines before creating a branch or issue?

Enforce contribution guidelines by validating prerequisites and strictly adhering to repository templates before creating branches, issues, or pull requests. This prevents non-compliant changes and ensures necessary information is captured consistently.

How do I prevent non-compliant code changes from being pushed to a repository?

Prevent non-compliant pushes by upholding security boundaries and validating prerequisites before submitting changes. The workflow ensures no commands are executed from docs and strict template adherence is maintained.

Does this contribution workflow support standardized issue and PR templates?

Yes, the contribution workflow supports standardized issue and PR templates to capture necessary information and maintain consistency. It enforces strict adherence to these templates across all repository contributions.

What are the limitations of enforcing strict contribution guidelines across repository issues and pull requests?

The guideline enforcement requires strict adherence to templates and validation steps before pushing changes, meaning contributors cannot bypass these checks or execute commands from docs, which may restrict rapid informal edits.