Added usage documentation

[Abhishek-gitty]

Summary by CodeRabbit

• Documentation
  • Added a usage guide with step-by-step instructions for running the project.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fb3ce777-1826-482e-9a26-2ed3fbc9392b

📥 Commits

Reviewing files that changed from the base of the PR and between a302e5f and 915b1e3.

📒 Files selected for processing (1)

• docs/usage/usage.md

---

Walkthrough

A new documentation file was added to provide user guidance on running the project. The "Usage Guide" includes a "Running the Project" section with instructions for executing three Python module commands related to baseline generation, regression testing, and benchmarking.

Changes

Cohort / File(s)	Summary
Documentation docs/usage/usage.md	New usage guide file with instructions for running project commands (generate-baselines, regress, bench).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

documentation

🚥 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 'Added usage documentation' accurately describes the main change: a new usage documentation file with a usage guide and running instructions.
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 unit tests (beta)

• Create PR with unit tests

---

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

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

[Aaryan-Dadu]

the doc is just too short for a user to understand anything

[Aaryan-Dadu]

Please add demo screenshots of your changes too

[Aaryan-Dadu]

Please add Fixes #Issue-Number in your PR description to link the issue to the PR.