Update skills-essential.txt

[JarbasAl]

add https://github.com/OpenVoiceOS/ovos-skill-diagnostics to default skills

Summary by CodeRabbit

• Chores
  • Updated the project's core dependency requirements to incorporate an essential package with a specific version range, ensuring improved functionality and compatibility.

[coderabbitai]

Walkthrough

A new dependency has been added to the project’s essential skills file. The update introduces the ovos-skill-diagnostics package with a version constraint of >=0.0.2 and <1.0.0, expanding the list of required skills for the project.

Changes

File	Change Summary
requirements/skills-essential.txt	Added new dependency: ovos-skill-diagnostics>=0.0.2,<1.0.0

Possibly related PRs

• requirements:latest stable packages #563: Updates similar dependency constraints in the same file, relating closely to this change.

Suggested labels

fix

Suggested reviewers

• goldyfruit
• j1nx

Poem

I'm a rabbit, hopping through the code,
Adding dependencies on this joyous road,
A new line in the file shines bright,
With version constraints keeping it light,
Celebrate the change—hop on with delight! 🐰

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ac45b8 and 65fa6a9.

📒 Files selected for processing (1)

• requirements/skills-essential.txt (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: end2end_tests (3.11)

🔇 Additional comments (1)

requirements/skills-essential.txt (1)

8-8: Dependency Addition Approved.
The line ovos-skill-diagnostics>=0.0.2,<1.0.0 has been correctly added to the list. Please verify that the specified version range aligns with the diagnostics skill’s API expectations and does not introduce conflicts with other skills.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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 generate docstrings to generate docstrings for this 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.81%. Comparing base (23f0bab) to head (65fa6a9).
Report is 198 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #656      +/-   ##
==========================================
- Coverage   75.33%   69.81%   -5.53%     
==========================================
  Files          15       15              
  Lines        3094     1653    -1441     
==========================================
- Hits         2331     1154    -1177     
+ Misses        763      499     -264     

Flag	Coverage Δ
end2end	53.72% <ø> (?)
unittests	46.40% <ø> (-28.94%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.