fix: skilljson

[JarbasAl]

Summary by CodeRabbit

• New Features

  • Introduced a new "Volume Control" functionality, allowing users to control volume using verbal commands.
  • Added a comprehensive list of example commands for user interaction with the volume control system.

• Bug Fixes

  • Removed outdated metadata for the "Volume Control" skill, streamlining the skill's configuration.

• Chores

  • Deleted several scripts related to version management and skill preparation, optimizing the codebase.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request involve the addition of a new JSON file for the "Volume Control" feature within the OVOS system, which provides commands for controlling volume via voice. Concurrently, several scripts related to version control and skill preparation have been removed, including those for managing version increments and preparing translations. The removed scripts contained various functionalities for handling version numbers and managing skill resources but are no longer part of the codebase.

Changes

File Path	Change Summary
locale/en-us/skill.json	Added a new JSON file for "Volume Control" with name, description, example commands, and tags.
res/desktop/skill.json	Removed JSON metadata for the "Volume Control" skill.
scripts/bump_alpha.py	Removed script for incrementing the alpha version number.
scripts/bump_build.py	Removed script for incrementing the build version number.
scripts/bump_major.py	Removed script for incrementing the major version number.
scripts/bump_minor.py	Removed script for incrementing the minor version number.
scripts/prepare_skillstore.py	Removed script for preparing and managing skills for OpenVoiceOS.
scripts/prepare_translations.py	Removed script for preparing translation files from the locale directory.
scripts/remove_alpha.py	Removed script for resetting the alpha version number to zero.
scripts/translate.py	Removed script for translating text files using the LibreTranslate API.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant OVOS
    participant VolumeControl

    User->>OVOS: Issue volume command (e.g., "set volume to maximum")
    OVOS->>VolumeControl: Process command
    VolumeControl-->>OVOS: Execute volume change
    OVOS-->>User: Confirm action

Loading

🐰 "In the code, a change took flight,
A volume control, oh what a delight!
With commands to mute and set it high,
Now our voices can reach the sky!
Scripts removed, but new paths we pave,
In the world of sound, we are brave!" 🎶

Warning

Rate limit exceeded

@github-actions[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 2 minutes and 24 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between cd14291 and 19eabee.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.