skills.rest
lightseekorg
lightseekorgOFFICIAL
Explore all skills by this author →
Website𝕏@lightseekorgGitHub

contribute

Run five quality gates for PR readiness verification.

11|2|Updated Mar 2, 2026
Search Tags:#formatting#quality-gate#lint#code-review#pull-request#conventional-commits
One-click install
npx skills add https://github.com/lightseekorg/smg-dev-guide --skill contribute-lightseekorg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: contribute
Source: https://github.com/lightseekorg/smg-dev-guide/tree/main/skills/contribute
Command: npx skills add https://github.com/lightseekorg/smg-dev-guide --skill contribute-lightseekorg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents shipping unverified code by enforcing a five-step quality gate before PRs are opened or merged.

Core Features & Use Cases

  • Enforced gate checks: FORMAT, LINT, TEST, BINDINGS, and COMMIT FORMAT to guarantee code quality.
  • Governance and compliance: ensures conventional commits and DCO sign-off for traceable changes.
  • Use Case: Teams adopting SMG workflows can reliably gate code changes, reducing post-merge defects.

Quick Start

Run all five gates locally before pushing a PR.

Frequently Asked Questions about contribute

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

FAQPage Schema
How do I automate pull request readiness checks for Rust code formatting and linting?▼

Automate pull request readiness by enforcing a five-step quality gate that validates formatting, linting, tests, bindings, and commit standards before merging. It requires running cargo +nightly fmt and cargo clippy with all features enabled.

What is a pre-merge quality gate for conventional commits and how does it work?▼

A pre-merge quality gate validates code changes by enforcing format, lint, test, and commit standards. It ensures conventional commits with DCO sign-off for traceable changes, preventing unverified code from being merged into the repository.

How do I enforce conventional commits with DCO sign-off before opening a PR?▼

Enforce conventional commits with DCO sign-off by applying a commit format quality gate. This governance step ensures all pull requests contain traceable, signed-off changes before they are opened or merged into the codebase.

Do I need cargo nightly and make to run local quality gate checks before pushing?▼

Yes, running local quality gate checks requires cargo +nightly for formatting, cargo clippy for linting, cargo test for testing, and make python-dev for bindings verification before pushing a pull request.

What is the best way to prevent unverified code from shipping in a software development workflow?▼

The best way to prevent shipping unverified code is enforcing a five-step quality gate covering formatting, linting, tests, bindings, and commit standards before pull requests are opened, reducing post-merge defects in team workflows.

Why does my pull request fail the lint gate when running cargo clippy?▼

Pull requests fail the lint gate when cargo clippy --all-targets --all-features -- -D warnings detects issues. The quality gate enforces zero warnings, ensuring all code meets strict linting standards before merging.

Related Skills

Explore More Software Engineering Skills→
OpenZeppelinOpenZeppelin
203

setup-stellar-contracts

Set up Soroban/Stellar smart contract projects with OpenZeppelin Rust crate dependencies.

Official
Intermediate
CODE-SAURABHCODE-SAURABH
2

release-engineer

Coordinate software releases from code review through production deployment and rollback readiness.

Community
Advanced
heyu-aiheyu-ai

ci-triage

Diagnose CI pipeline failures in Python, JavaScript, and Go stacks.

Official
Intermediate
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced