Skip to content

Add XVARY Stock Research (Claude Code skill)#210

Open
SenSei2121 wants to merge 1 commit intoPatrickJS:mainfrom
SenSei2121:add-xvary-stock-research
Open

Add XVARY Stock Research (Claude Code skill)#210
SenSei2121 wants to merge 1 commit intoPatrickJS:mainfrom
SenSei2121:add-xvary-stock-research

Conversation

@SenSei2121
Copy link

@SenSei2121 SenSei2121 commented Mar 24, 2026

Adds xvary-research/claude-code-stock-analysis-skill — MIT, public SEC EDGAR + market data workflow (/analyze, /score, /compare) for Claude Code / compatible agents.

Inserted as a short README section before Contributing/License where possible.

Summary by CodeRabbit

  • Documentation
    • Added XVARY Stock Research section with external project reference and license information.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 24, 2026

📝 Walkthrough

Walkthrough

A new "XVARY Stock Research" section was added to the README with a link to an external GitHub project and a brief description of its functionality and license information.

Changes

Cohort / File(s) Summary
Documentation
README.md
Added new "XVARY Stock Research" section with external project link and description.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A carrot link now graces the page,
To XVARY's wisdom and technical sage,
The README hops with fresh insight,
Project discovery—a README's delight! 🐰📚

🚥 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 accurately and specifically describes the main change: adding a new README section about XVARY Stock Research, a Claude Code skill project.
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

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

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Around line 312-315: Move the "XVARY Stock Research" entry out of the
top-level and into the appropriate existing section (e.g., the "## Utilities" or
"## Directories" subsection) and insert it in alphabetical order among that
section's items; convert the absolute URL to a relative repository link (use ./
or appropriate relative path), update the Table of Contents to reflect the moved
section if needed, and ensure the entry formatting matches other items in the
README (same bullet style and link format).

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: af458cbf-3247-4a76-a8a3-9a0f50eb12a2

📥 Commits

Reviewing files that changed from the base of the PR and between fc2ce04 and 321aee4.

📒 Files selected for processing (1)
  • README.md

Comment on lines +312 to +315
## XVARY Stock Research

- [XVARY Stock Research](https://github.com/xvary-research/claude-code-stock-analysis-skill) — Claude Code skill for public SEC EDGAR + market data: `/analyze`, `/score`, `/compare`. MIT.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Move this entry into an existing section and align with README conventions.

This new top-level section breaks the prescribed README order, leaves the table of contents outdated, and introduces an absolute link where the guideline requires relative links. Please place this item under the appropriate existing section (likely ## Utilities or ## Directories), keep alphabetical order there, and update TOC accordingly.

As per coding guidelines, “Maintain the following structure in the README.md file: 1. Title and Awesome badge 2. Logo 3. Short description 4. "Why .cursorrules?" section 5. Table of Contents 6. Rules section (with subcategories) 7. How to Use section 8. Contributing section 9. License section”, “Ensure all links in the README.md file are relative and correct”, and “When updating the README.md, ensure the table of contents remains accurate.”

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@README.md` around lines 312 - 315, Move the "XVARY Stock Research" entry out
of the top-level and into the appropriate existing section (e.g., the "##
Utilities" or "## Directories" subsection) and insert it in alphabetical order
among that section's items; convert the absolute URL to a relative repository
link (use ./ or appropriate relative path), update the Table of Contents to
reflect the moved section if needed, and ensure the entry formatting matches
other items in the README (same bullet style and link format).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant