skills.rest
WanxiaJaneYang
WanxiaJaneYangCOMMUNITY
Explore all skills by this author →
GitHub

repo-standards

Validate code formatting, linting, type-checking, and tests for pull requests.

Updated Feb 11, 2026
Search Tags:#code quality#workflow#pull request#validation#repository#standards
One-click install
npx skills add https://github.com/WanxiaJaneYang/mvp-agent --skill repo-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: repo-standards
Source: https://github.com/WanxiaJaneYang/mvp-agent/tree/main/.codex/skills/repo-standards
Command: npx skills add https://github.com/WanxiaJaneYang/mvp-agent --skill repo-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that changes made to the repository adhere to established standards, streamlining the development process and maintaining code quality.

Core Features & Use Cases

  • Repository Inspection: Checks the current state of the repository before making changes.
  • Change Validation: Guides users to run relevant validation checks (format, lint, tests) for modified areas.
  • Documentation Updates: Reminds users to update documentation when workflows or behavior change.
  • Use Case: Before submitting a Pull Request, use this Skill to ensure all necessary checks have been performed and documentation is up-to-date.

Quick Start

Use the repo-standards skill to review and prepare your changes for a pull request.

Frequently Asked Questions about repo-standards

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

FAQPage Schema
How do I validate code changes before submitting a pull request?▼

To validate code changes before a pull request, inspect the repository state and run formatting, linting, type-checking, and testing checks to ensure adherence to established standards.

What is the best way to maintain repository standards during development?▼

Maintaining repository standards involves enforcing code quality and consistency by validating modified areas and ensuring documentation accurately reflects any changes in workflows or behavior.

Does this repository validation check formatting and linting automatically?▼

No, this validation guides users to run relevant formatting, linting, type-checking, and testing checks manually for modified areas rather than executing them automatically.

When do I need to update documentation for a pull request?▼

You need to update documentation for a pull request when changes in commands, workflows, or behavior occur, ensuring the repository accurately reflects the current state.

Can I use this to check repository state before modifying code?▼

Yes, you can use this to perform repository inspection, checking the current state of the repository to understand existing standards before making modifications.

What are the limitations of manual code change validation?▼

The limitation is that it requires manual execution of validation checks like format and lint, meaning it guides the workflow but does not automatically execute or enforce the build checks.

Related Skills

Explore More Software Engineering Skills→
HouseofmvpsHouseofmvps
115

code-review

Review modified code for correctness, security, performance, and architecture flaws.

Community
Advanced
billlzzz26billlzzz26
4

create-pull-request

Create a GitHub pull request using the repository's PR template and required metadata.

Community
Intermediate
randalmurphalrandalmurphal

Python Style Standards

Enforce Python style standards with ruff, pylint, and mypy.

Community
Advanced
VoDaiLoczVoDaiLocz
24

lint-and-validate

Automate linting and static analysis of code in CI pipelines.

Community
Intermediate