Storj Commit Style

This skill configures Aider to follow Storj project commit conventions used in the storj/storj decentralized cloud object storage repository.

What This Skill Does

Instructions for AI Agent

When making commits in a Storj repository:

1. **Always use the scope:message format**: Start commits with a scope identifier followed by a colon and descriptive message. Examples:

- `satellite/metainfo: add validation`

- `storagenode/piecestore: fix download timeout`

- `web/satellite: update dashboard UI`

2. **Choose appropriate scope**: The scope should reference the component or subsystem being modified (e.g., `satellite`, `storagenode`, `uplink`, `web/satellite`, `satellite/metainfo`).

3. **Never add AI attribution**: Do not include lines like "Co-Authored-By", "Generated-By", or any other AI attribution metadata in commit messages. Keep commits clean and focused on the change itself.

4. **Keep messages concise**: Write clear, imperative-mood messages that describe what the commit does (e.g., "add validation" not "added validation").

Configuration Details

Examples

Good commits:

```

satellite/metainfo: add validation for segment size

storagenode/orders: fix settlement deadline calculation

web/satellite: improve billing history display

```

Bad commits:

```

Add validation (missing scope)

satellite/metainfo: Added validation for segment size (wrong tense)

satellite: fix bug

Co-Authored-By: AI Assistant <[email protected]> (unwanted attribution)

```

Constraints