Dev Rules

Use when writing code, making git operations, handling secrets, reviewing PRs, or working with dependencies. Enforces git safety, security best practices, PR workflow discipline, and context-efficient development patterns. Auto-activates as guardrails.

5 starsGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Sagargupta16/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Sagargupta16/claude-skills --skill dev-rules
Manual install
git clone --depth 1 https://github.com/Sagargupta16/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/dev-rules/skills/dev-rules ~/.claude/skills/dev-rules

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Development Rules and Guardrails

## Git Safety

| Rule | Why |
|------|-----|
| Never force push to main/master | Destroys team history, breaks CI |
| Never `git reset --hard` without confirmation | Irreversible data loss |
| Never amend published commits | Creates divergent history for collaborators |
| Never skip pre-commit hooks (`--no-verify`) | Hooks catch real issues |
| Stage specific files by name | `git add .` risks committing secrets or binaries |
| Never commit .env, credentials, API keys | Secrets in git history are permanent |
| Verify current branch before pushing | Avoid pushing to wrong branch |

## Security

### Secrets and Credentials
- Never commit `.env` files, API keys, tokens, passwords, or connection strings
- Always use `.env.example` with placeholder values, never real credentials
- If real credentials are found in git history, flag immediately - they must be rotated
- Add secret config files to `.gitignore` (e.g., `config/secrets.yml`)

### Code Security
- Validate all user input at system boundaries (API endpoints, form submissions)
- Use parameterized queries - never string concatenation for database queries
- Sanitize data before rendering in templates (prevent XSS)
- Use bcrypt or argon2 for password hashing, never MD5 or SHA for passwords
- Set CORS origins from environment variables, never wildcard in production

### Dependency Security
- Check for known vulnerabilities before adding new packages
Read the full skill on GitHub

Details

Skill name
dev-rules
Path
plugins/dev-rules/skills/dev-rules/SKILL.md
License
MIT
Repo updated
13 November 2026

FAQ

What does the Dev Rules skill do?

Use when writing code, making git operations, handling secrets, reviewing PRs, or working with dependencies. Enforces git safety, security best practices, PR workflow discipline, and context-efficient development patterns. Auto-activates as guardrails.

How do I install the Dev Rules skill?

Claude Code plugin: /plugin marketplace add Sagargupta16/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Dev Rules popular?

It lives in Sagargupta16/claude-skills, which has 5 GitHub stars and 0 forks.

Related skills

Clean Code

5

Sagargupta16/claude-skills

Use when the user writes new Python, or asks for review, refactor, or cleanup of Python code, names, comments/docstrings, functions, or tests. Applies Robert Martin's complete Clean Code catalog -- naming, functions, comments, DRY, boundary conditions, and tests -- to the code being changed.

Software Development

Context Management

5

Sagargupta16/claude-skills

Use when managing Claude Code context window during long sessions, when context feels degraded, or when deciding between /compact, /clear, /rewind, and sub-agents. Covers context rot detection, compaction timing, branching strategy, and sub-agent isolation patterns.

AI, LLMs & Agents

Debug Triage

5

Sagargupta16/claude-skills

Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.

Software Development

Diff Explain

5

Sagargupta16/claude-skills

Use when you want a one-paragraph plain-English summary of what a diff does. Activates on "summarize this diff", "what does this PR do", "explain this branch", or when pointed at a PR URL or local branch.

Git & Code Review

Copilot PR Autopilot

9

sandbaseai/workbuddy-skill

Use when explicitly asked to run a bounded Copilot PR review loop, triage threads, verify fixes, and prepare a clean merge decision.

Git & Code Review

Finishing a Development Branch

9

sandbaseai/workbuddy-skill

Use when implementation is complete and you need to verify the merged result, integrate the branch safely, publish it, and remove only disposable development state.

Git & Code Review

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.