Storj Commit Style

This skill configures Aider to follow the Storj v3 project's commit message conventions for their decentralized cloud object storage platform.

What This Skill Does

Instructions

When committing changes to the Storj codebase:

1. **Commit Message Format**

- Always use the format: `{scope}: {message}`

- The scope should match the component or package being modified

- Example scopes: `satellite/metainfo`, `storagenode/orders`, `uplink/piecestore`

- Keep messages concise and descriptive

- Use lowercase for the message portion

- Example: `satellite/metainfo: add validation for segment size`

2. **AI Attribution**

- NEVER add AI attribution lines to commits

- Do not add "Co-Authored-By" lines

- Do not add any additional metadata about AI involvement

- Keep commits clean with only the required message format

3. **File Handling**

- Do not modify or commit changes to `.gitignore` files

- Preserve existing `.gitignore` entries

4. **Scope Selection Guidelines**

- Use the directory path as the scope when modifying a specific package

- For multi-package changes, use the primary affected component

- Common scopes include: `satellite`, `storagenode`, `uplink`, `multinode`, `web`

- For subdirectories, use the full path: `satellite/metainfo`, `storagenode/piecestore`

Configuration Settings

Examples

**Good commit messages:**

**Bad commit messages:**

Notes

This configuration is specifically designed for the Storj v3 decentralized cloud storage project and maintains their established commit conventions for consistent version control history.