feat: Create hello world script

[pokryfka]

Task

Create hello world script

Plan

1. Create a new file named scripts/hello.py.
2. Add a shebang line to the top of the file to indicate it should be run with python3: #!/usr/bin/env python3.
3. Add the python code to print 'Hello, World!' to the console: print('Hello, World!').
4. Make the script executable using the command chmod +x scripts/hello.py.

Summary by CodeRabbit

• Chores
  • Added a new Python script to the repository.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new executable Python script is added to the scripts directory that prints "Hello, World!" to stdout. The script contains a shebang line for Python 3 and a single print statement, totaling two lines of code with no additional logic or error handling.

Changes

Cohort / File(s)	Summary
New Hello World Script scripts/hello.py	Added executable Python script with shebang and single print statement outputting "Hello, World!"

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A script so simple, pure and bright,
Just two wee lines of code delight,
"Hello, World!" echoes through the air,
A bunny's gift, with gentle care! 🌍✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: Create hello world script' directly and clearly summarizes the main change - creating a new hello world script file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch agent/create-hello-world-script-5fa3759d

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

scripts/hello.py (1)

1-2: Consider adding the standard future annotations import.

The script works correctly, but per the project's coding guidelines, Python modules should include from __future__ import annotations.

Suggested change

 #!/usr/bin/env python3
+from __future__ import annotations
+
 print('Hello, World!')

As per coding guidelines: "Include from __future__ import annotations in every Python module".

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@scripts/hello.py` around lines 1 - 2, Add the required future annotations
import at the top of the module: insert "from __future__ import annotations" as
the first non-shebang line in scripts/hello.py so the module follows the
project's coding guideline; ensure it appears before any other statements (e.g.,
before the existing print('Hello, World!')).

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@scripts/hello.py`:
- Around line 1-2: Add the required future annotations import at the top of the
module: insert "from __future__ import annotations" as the first non-shebang
line in scripts/hello.py so the module follows the project's coding guideline;
ensure it appears before any other statements (e.g., before the existing
print('Hello, World!')).

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 42490e98-1cda-4863-ab3e-3b90709475fb

📥 Commits

Reviewing files that changed from the base of the PR and between 4f5cd42 and 6bfdcc1.

📒 Files selected for processing (1)

• scripts/hello.py