Add or update project-specific rules in the .claude/rules/ directory.
npx skills add https://github.com/Vekta/PolyForge --skill add-rule-vekta
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
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.
/add-rule to enforce this convention across your project's workflow.Use the add-rule skill to add the rule that all new components must have associated unit tests.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
forecast-bioDump project rules, git state, issues, and hook configurations for reorientation.
NVIDIARun tests, coverage checks, and sanity plots on Earth2Studio data sources.
paultyngAutomate Git pre-commit checks, changelog generation, and GitHub pull request updates.
inbharataiGenerate, format, and convert Markdown documents for README files, wikis, and changelogs.