Storj Commit Style

Enforces commit message conventions for the Storj decentralized cloud storage project.

Overview

This skill configures commit behavior for Storj v3 development, ensuring commits follow the project's scope-based format without AI attribution.

Instructions

When committing changes:

1. **Commit Message Format**

- Use the format: `{scope}: {message}`

- Scope represents the component or area being modified (e.g., `satellite/metainfo`, `storagenode/orders`, `uplink/download`)

- Message is a concise description of the change

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

2. **Attribution Rules**

- NEVER add AI attribution to commits

- Do not modify the author field

- Do not modify the committer field

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

- Commits should appear as if written entirely by the human developer

3. **Git Configuration**

- Gitignore files are tracked (not ignored during commits)

- Standard Git attribute settings for committer information are disabled

Examples

**Good commits:**

```

satellite/metainfo: add validation for segment size

storagenode/orders: fix settlement calculation

uplink/download: improve retry logic for failed pieces

```

**Bad commits:**

```

Add validation (missing scope)

satellite/metainfo: add validation

Co-Authored-By: Claude <...> (has AI attribution)

```

Constraints