# Standardize Team Development Conventions

Teams often lose time when project structure, commits, reviews, and configuration practices differ between contributors. This skill gives Claude, Codex, and Claude Code a shared checklist for consistent development conventions.

## Install

```bash
npx skillstore add devanb/global-conventions
```

## Metadata

- Status: approved
- Slug: devanb-global-conventions
- Skillstore revision: r1
- Version status: missing
- Tree hash: 9e60fba0e773ee1893f4eb46e49c1d80ab2b374653a7435bec97db7baf4c7a2f
- Author: DevanB
- GitHub username: DevanB
- License: MIT
- Repository: https://github.com/DevanB/lucidlog/tree/master/.claude/skills/global-conventions
- Ref: 0519034dad657fb1f7706e0550e962beeda73fdf
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem
- Quality score: 79
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/devanb-global-conventions
- Manifest: https://skillstore.pages.dev/api/skills/devanb-global-conventions/manifest

## Capabilities

- Directs agents to apply project organization and directory conventions.
- Guides commit messages, branch choices, and pull request practices.
- Covers environment variable and configuration documentation workflows.
- Supports review, testing, changelog, and release note consistency.
- Advises on feature flags, dependencies, and contribution guidelines.

## Use Cases

- Align Pull Request Practices: Use the skill to plan branches, commits, tests, review notes, and documentation before opening a pull request.
- Maintain Contribution Consistency: Apply shared expectations for changelogs, setup notes, dependencies, and contribution guidance across repeated community changes.
- Guide Agent Workflows: Ask an AI coding agent to check structure, configuration, testing, and release notes against the same conventions.

## Prompt Templates

### Apply Project Conventions

```
Review my current task against the global conventions. Focus on file placement, documentation needs, and testing expectations before making changes.
```

### Prepare a Pull Request

```
Create a pull request plan that follows our global conventions. Include branch naming, commit style, review notes, tests, and documentation updates.
```

### Audit Workflow Consistency

```
Audit this repository for convention drift. Compare structure, configuration handling, changelog habits, and review process against the global conventions.
```

### Resolve Process Tradeoffs

```
Help decide whether this unfinished feature should use a feature flag or a long-lived branch. Explain the tradeoffs using the global conventions.
```

## Limitations

- The skill delegates detailed rules to a linked conventions document.
- It does not execute scripts or inspect repositories by itself.
- It does not replace project-specific policies, legal review, or security approval.
- The referenced conventions file must be available to the agent.

## Best Practices

- Use the conventions before starting repository organization or pull request work.
- Keep the referenced standards document available and current.
- Ask for explicit testing and documentation checks before final review.

## Anti Patterns

- Do not use the skill as a substitute for missing project policies.
- Do not rely on it when the referenced conventions file is unavailable.
- Do not let convention guidance override security or compliance requirements.

## Security Audit

- Audited at: 2026-07-09T11:15:37.765\+00:00
- Summary: The static path traversal finding is confirmed because SKILL.md line 28 instructs the agent to follow a ../../../ link outside the skill directory. No prompt injection, data exfiltration, network access, or command execution evidence was found in the scanned file.

## Stats

- Views: 220
- Downloads: 8
- Favorites: 0
- Popularity score: 0