add-rule

Name: add-rule
Availability: InStock
Author: Vekta

Add or update project-specific rules in the .claude/rules/ directory.

2|1|Updated Mar 10, 2026

Search Tags:#git #workflow #project management #coding standards #conventions #rules

Ready to run

npx skills add https://github.com/Vekta/PolyForge --skill add-rule-vekta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-rule
Source: https://github.com/Vekta/PolyForge/tree/main/skills/add-rule
Command: npx skills add https://github.com/Vekta/PolyForge --skill add-rule-vekta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill allows users to add or update project-specific rules and conventions without needing to re-run the main /forge command, ensuring consistency and adherence to best practices.

Core Features & Use Cases

Rule Management: Add new rules to specific scopes (e.g., backend, frontend, tests).
Learning from PRs: Extract conventions and rules directly from existing pull request feedback.
Use Case: You've identified that all commit messages should follow a specific format. Use /add-rule to enforce this convention across your project's workflow.

Quick Start

Use the add-rule skill to add the rule that all new components must have associated unit tests.

Frequently Asked Questions about add-rule

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

FAQPage Schema

How do I add coding conventions and rules to my project workflow?▼

To add coding conventions, you can define project-specific rules interactively or via direct text input. The system stores these guidelines in the .claude/rules/ directory, ensuring your project workflow adheres to consistent standards.

Can I extract coding standards directly from existing pull request feedback?▼

Yes, you can extract coding standards from pull request feedback. The system learns conventions directly from PR comments and adds them to your project rules, automating the enforcement of best practices.

How do I scope project rules to specific directories like frontend or backend?▼

You can scope project rules to specific directories by defining the target scope during rule addition. This ensures conventions are applied appropriately, whether targeting frontend, backend, or general project guidelines.

What is the best way to enforce commit message formats without re-running the entire workflow setup?▼

To enforce commit message formats without re-running full workflow setup, use the targeted rule addition command. This directly updates your project conventions in the rules directory, maintaining consistency across your git workflow.

Do I need to manually organize rules in the .claude/rules/ directory?▼

No, you do not need to manually organize rules in the .claude/rules/ directory. The system automatically manages the addition and updating of your project-specific rules and conventions within this location.

Why are my newly added coding conventions not applying to my tests?▼

If coding conventions are not applying to tests, verify the rule scope. Conventions must be explicitly scoped to the test directory or defined as general project guidelines to ensure proper adherence.