Instruction file imported from explosivo22/aiorinnai (.github/instructions/commits.instructions.md). Copyright stays with the author.

Conventional Commits Instructions

Name: commits
Author: explosivo22

Always follow the Conventional Commits specification when creating commit messages.

Commit Message Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types

Use one of the following types:

Type	Description
`feat`	A new feature
`fix`	A bug fix
`docs`	Documentation only changes
`style`	Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
`refactor`	A code change that neither fixes a bug nor adds a feature
`perf`	A code change that improves performance
`test`	Adding missing tests or correcting existing tests
`build`	Changes that affect the build system or external dependencies
`ci`	Changes to CI configuration files and scripts
`chore`	Other changes that don't modify src or test files
`revert`	Reverts a previous commit

Rules

Type is required - Every commit must have a type prefix
Description is required - A short summary of the code changes (imperative mood, lowercase, no period at end)
Scope is optional - A noun describing a section of the codebase (e.g., api, device, auth)
Body is optional - Provide additional contextual information about the code changes
Footer is optional - Used for breaking changes and issue references
Breaking changes - Must be indicated by ! after type/scope OR by BREAKING CHANGE: in footer
Keep the subject line under 50 characters when possible
Wrap the body at 72 characters

Examples

Simple feature

feat: add water heater temperature control

Feature with scope

feat(api): add authentication token refresh

Bug fix with body

fix(device): correct temperature unit conversion

The API returns Fahrenheit but was being treated as Celsius.
Added proper conversion logic in the device module.

Breaking change with footer

feat(api)!: change authentication flow to OAuth2

BREAKING CHANGE: The API now requires OAuth2 tokens instead of API keys.
Users must update their authentication configuration.

Closes #123

Documentation

docs: update README with installation instructions

Multiple footers

fix(auth): resolve token expiration issue

The refresh token was not being properly stored after renewal.

Fixes #456
Reviewed-by: John Doe

Scope Suggestions for This Project

api - Changes to aiorinnai/api.py
device - Changes to aiorinnai/device.py
user - Changes to aiorinnai/user.py
types - Changes to type definitions
errors - Changes to error handling
deps - Dependency updates
ci - CI/CD configuration changes

{ "ocm": "1", "id": "explosivo22-aiorinnai-commits-instructions", "kind": "skill", "name": "commits", "description": "Always follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification when creating commit messages.", "publisher": "explosivo22", "version": "1.0.0", "capabilities": { "domains": [ "math" ], "tags": [ "skill-md", "github-instructions" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Always follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification when creating commit messages." ], "primary": false, "metadata": { "source": { "provider": "github-instructions", "repository": "https://github.com/explosivo22/aiorinnai", "path": ".github/instructions/commits.instructions.md", "ref": "5692be33fdfbfeb20f819fb31cdba2b1181651a8", "url": "https://github.com/explosivo22/aiorinnai/blob/5692be33fdfbfeb20f819fb31cdba2b1181651a8/.github/instructions/commits.instructions.md", "key": "explosivo22/aiorinnai/.github/instructions/commits.instructions.md" }, "applies_to": "**" }, "instructions": "# Conventional Commits Instructions\n\nAlways follow the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification when creating commit messages.\n\n## Commit Message Format\n\n```\n<type>[optional scope]: <description>\n\n[optional body]\n\n[optional footer(s)]\n```\n\n## Types\n\nUse one of the following types:\n\n| Type | Description |\n|------|-------------|\n| `feat` | A new feature |\n| `fix` | A bug fix |\n| `docs` | Documentation only changes |\n| `style` | Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc) |\n| `refactor` | A code", "cost": { "context_tokens": 704 } }

commits

About