From 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.
npx claudepluginhub sagargupta16/claude-skills --plugin dev-rulesThis skill uses the workspace's default tool permissions.
| Rule | Why |
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
| 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 |
.env files, API keys, tokens, passwords, or connection strings.env.example with placeholder values, never real credentials.gitignore (e.g., config/secrets.yml)When working with pull requests:
gh api repos/{owner}/{repo}/issues/{num}/commentsgh api repos/{owner}/{repo}/pulls/{num}/commentsgh api repos/{owner}/{repo}/pulls/{num} --jq '{mergeable, mergeable_state, draft}'gh api repos/{owner}/{repo}/compare/{base}...{head} --jq '{behind_by, ahead_by}'--help first to understand their interface--help is insufficient or if debugging