Storj Commit Style

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

What This Skill Does

Ensures all commits follow Storj's specific format requirements:

Uses `{scope}: {message}` pattern (e.g., `satellite/metainfo: add validation`)

Prevents AI attribution in commits (no author, committer, or co-author tags)

Maintains clean commit history without AI-generated metadata

The skill applies these Aider settings:

1. **gitignore: false** - Does not respect .gitignore when showing files to AI

2. **attribute-committer: false** - Disables AI committer attribution

3. **commit-prompt** - Enforces Storj commit message format

All commits must follow this pattern:

```

{scope}: {message}

```

**Examples:**

`satellite/metainfo: add validation`

`storagenode/pieces: fix concurrent access bug`

`uplink: improve error handling`

The scope typically indicates the component or subsystem (satellite, storagenode, uplink, etc.) followed by an optional subcomponent.

**NO AI attribution**: Never add "Co-Authored-By", "Author", or any AI-related metadata to commits

**Clean history**: Commits should appear as normal developer commits

**Scope prefix required**: Always include the scope before the message

**Lowercase convention**: Messages typically start lowercase after the scope

When you commit changes to satellite metadata validation:

```

satellite/metainfo: add validation

```

When fixing a bug in storage node piece handling:

```

storagenode/pieces: fix concurrent access bug

```

When improving uplink client error messages:

```

uplink: improve error handling

```