skills.rest
thrillmade
thrillmadeOFFICIAL
Explore all skills by this author →
GitHub

respect-existing-conventions

Evaluates pull request changes for compliance with existing code conventions.

1|Updated May 15, 2026
Search Tags:#code review#code consistency#code conventions#convention enforcement#pattern adherence
One-click install
npx skills add https://github.com/thrillmade/agent-skills --skill respect-existing-conventions
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: respect-existing-conventions
Source: https://github.com/thrillmade/agent-skills/tree/main/.claude/skills/respect-existing-conventions
Command: npx skills add https://github.com/thrillmade/agent-skills --skill respect-existing-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain a uniform codebase by enforcing adherence to established coding conventions and patterns, reducing unnecessary refactoring and promoting consistency.

Core Features & Use Cases

  • Adhere to Existing Patterns: Prompts for adherence to established conventions to avoid unnecessary changes.
  • Prevent Redundant Refactoring: Helps avoid refactoring when it's not needed, saving time and effort.
  • Use Case: When reviewing a pull request, this Skill will alert you if a change deviates from the codebase's established patterns without a compelling reason.

Quick Start

Apply the respect-existing-conventions skill during code reviews to ensure the pull request follows the codebase's conventions.

Frequently Asked Questions about respect-existing-conventions

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

FAQPage Schema
How do I enforce code conventions during a pull request review?▼

To enforce code conventions during a pull request review, apply an automated check that evaluates changes against established repository patterns and flags deviations. This maintains codebase consistency without requiring external dependencies.

What is the best way to prevent unnecessary code refactoring in pull requests?▼

The best way to prevent unnecessary code refactoring is to evaluate pull request changes against established codebase conventions. This flags deviations from existing patterns, saving time and effort by avoiding redundant modifications.

How does pattern adherence checking work in a repository?▼

Pattern adherence checking works by evaluating code changes within the pull request context against the repository's established conventions. It operates directly within the pull request environment without external dependencies to flag any deviations from existing patterns.

Do I need external dependencies to check for code consistency in pull requests?▼

No, you do not need external dependencies to check for code consistency. The convention enforcement process operates solely within the pull request context, evaluating changes against established patterns without requiring additional tools or setup.

When should I check for codebase consistency and pattern adherence?▼

You should check for codebase consistency and pattern adherence when reviewing a pull request. This alerts you if a change deviates from the codebase's established patterns without a compelling reason, preventing unnecessary refactoring.

Related Skills

Explore More Software Engineering Skills→
Omar-ObandoOmar-Obando
44

project-conventions

Discover and enforce existing project conventions before modifying code.

Community
Intermediate
kevinnftkevinnft
13

github-pr-workflow

Coordinate GitHub pull request lifecycles from branch creation to merge.

Community
Advanced
RelicWare-CoRelicWare-Co

ultracite

Automate linting and formatting setup for JavaScript and TypeScript projects.

Official
Basic
cartridge-ggcartridge-gg
80

pre-commit-check

Run Husky pre-commit hooks for format, lint, and test checks.

Official
Intermediate