enforcing-project-rules
Skill2 starsChanged 2 months agoBSD-3-ClauseView on GitHub
Enforces project-level operational rules that govern how the agent interacts with the workspace, CLI, and version control. What this does is enumerating governance rules that you should always follow when working in a project. Use this in ALL tasks executed inside a repository to ensure compliance with project constraints such as working directory rules and git branch restrictions. Use this skill also in Plan mode.
In this repository14 other files it gives its agents.
- AGENTS.mdAGENTS.md
- addressing-pull-request-commentsSkill
- analyzing-github-issueSkill
- applying-ruby-conventionsSkill
- applying-test-conventionsSkill
- committing-changesSkill
- creating-pull-requestSkill
- editing-filesSkill
- implementing-github-issueSkill
- improving-agent-reflectionSkill
- running-cli-in-wsl-portableSkill
- syncing-branch-with-baseSkill
- updating-docSkill
- validating-production-qualitySkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Always tell the user "SKILL: I am enforcing project rules" to inform the user that you are running this skill.
- Very specific: line 51
Always use it every time another skill specifically mentions skill: enforcing-project-rules.
- Distinctive: line 52
Always use it every time the user asks you to follow project rules.
- Distinctive: line 53
Always use it every time you implement a task in a project.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Enforcing project rules
Inform the user
- Always tell the user "SKILL: I am enforcing project rules" to inform the user that you are running this skill.
Non-negotiable Rules and Constraints to follow (MANDATORY)
Rule: Execute all CLI commands from the workspace's root directory
Example: Incorrect
cd scripts
./run_tests ../spec/*_spec.rbExample: Correct
./scripts/run_tests spec/*_spec.rbRationale
The API entry points and tools of a repository all have a consistent usage that does not depend on the caller context. Everything starts from the workspace root directory.
Rule: Use only the git branch that is already checked out
Example: Incorrect
git checkout {another_branch}
git switch {another_branch}Rationale
The current branch gives you a safe space to modify files without impacting other branches.
When to use it
- This skill can be used when in Plan mode.
- Always use it every time another skill specifically mentions
skill: enforcing-project-rules. - Always use it every time the user asks you to follow project rules.
- Always use it every time you implement a task in a project.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

