Conversation
📝 WalkthroughWalkthroughThis PR removes a large set of skill documentation, supporting guides, utilities, and a local Claude settings file from Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Fix all issues with AI agents
In `@AGENTS.md`:
- Line 20: Update the capitalization of the platform name in AGENTS.md by
changing the text segment that reads "workspace root
(`/Users/jim/Github/zenko`)" to use "GitHub" (e.g., "workspace root
(`/Users/jim/GitHub/zenko`)") so the product name is correctly capitalized;
locate the literal string "/Users/jim/Github/zenko" in AGENTS.md and replace
"Github" with "GitHub".
- Around line 20-21: Replace the hard-coded, user-specific path
'/Users/jim/Github/zenko' in AGENTS.md with a repo-relative instruction; update
the line "Run all commands from the **workspace root**
(`/Users/jim/Github/zenko`)" to simply instruct contributors to run commands
from the workspace/repo root (e.g., "Run all commands from the workspace root")
so the documentation is portable and does not reference a specific user's
filesystem.
- Around line 178-194: The fenced tree block in AGENTS.md (the block starting
with "zenko/") is missing a language tag which triggers markdownlint rule MD040;
update that fenced code block to include a language tag like "text" (e.g.,
change the opening ``` to ```text) so the repo-structure diagram is treated as
plain text and the linter warning is resolved.
AGENTS.md
Outdated
| - **Snapshots:** `bun zenko test -u` refreshes stored results. | ||
| - **Coverage:** `bun zenko coverage`. | ||
| - **Type check:** `bun zenko check-types` or `turbo check-types`. | ||
| Run all commands from the **workspace root** (`/Users/jim/Github/zenko`). |
There was a problem hiding this comment.
Minor doc polish: “GitHub” capitalization.
The path uses Github; the platform name is “GitHub.”
🔧 Suggested edit
-Run all commands from the **workspace root** (`/Users/jim/Github/zenko`).
+Run all commands from the **workspace root** (`/Users/jim/GitHub/zenko`).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Run all commands from the **workspace root** (`/Users/jim/Github/zenko`). | |
| Run all commands from the **workspace root** (`/Users/jim/GitHub/zenko`). |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~20-~20: The official name of this software platform is spelled with a capital “H”.
Context: ...l commands from the workspace root (/Users/jim/Github/zenko). ### Essential Commands | Com...
(GITHUB)
🤖 Prompt for AI Agents
In `@AGENTS.md` at line 20, Update the capitalization of the platform name in
AGENTS.md by changing the text segment that reads "workspace root
(`/Users/jim/Github/zenko`)" to use "GitHub" (e.g., "workspace root
(`/Users/jim/GitHub/zenko`)") so the product name is correctly capitalized;
locate the literal string "/Users/jim/Github/zenko" in AGENTS.md and replace
"Github" with "GitHub".
| ``` | ||
| zenko/ | ||
| ├── packages/ | ||
| │ ├── zenko/ # Main library | ||
| │ │ ├── src/ | ||
| │ │ │ ├── core/ # Schema & operation parsing | ||
| │ │ │ ├── utils/ # Helper functions | ||
| │ │ │ ├── types/ # TypeScript type definitions | ||
| │ │ │ └── __tests__/ | ||
| │ │ ├── private/ # Private test examples (not published) | ||
| │ │ └── dist/ # Build output (generated) | ||
| │ ├── examples/ # Example API clients | ||
| │ └── specs/ # OpenAPI test specifications | ||
| ├── turbo.json # Turborepo configuration | ||
| ├── .oxfmtrc.json # Formatter configuration | ||
| └── .oxlintrc.json # Linter configuration | ||
| ``` |
There was a problem hiding this comment.
Add a language tag to the fenced tree block.
The repo-structure code fence lacks a language spec, which trips markdownlint (MD040).
🔧 Suggested edit
-```
+```text
zenko/
├── packages/
│ ├── zenko/ # Main library
│ │ ├── src/
│ │ │ ├── core/ # Schema & operation parsing
│ │ │ ├── utils/ # Helper functions
│ │ │ ├── types/ # TypeScript type definitions
│ │ │ └── __tests__/
│ │ ├── private/ # Private test examples (not published)
│ │ └── dist/ # Build output (generated)
│ ├── examples/ # Example API clients
│ └── specs/ # OpenAPI test specifications
├── turbo.json # Turborepo configuration
├── .oxfmtrc.json # Formatter configuration
└── .oxlintrc.json # Linter configuration</details>
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.20.0)</summary>
[warning] 178-178: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
In @AGENTS.md around lines 178 - 194, The fenced tree block in AGENTS.md (the
block starting with "zenko/") is missing a language tag which triggers
markdownlint rule MD040; update that fenced code block to include a language tag
like "text" (e.g., change the opening totext) so the repo-structure
diagram is treated as plain text and the linter warning is resolved.
</details>
<!-- fingerprinting:phantom:triton:eagle -->
<!-- This is an auto-generated comment by CodeRabbit -->
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #65 +/- ##
=======================================
Coverage 97.32% 97.32%
=======================================
Files 16 16
Lines 2171 2171
=======================================
Hits 2113 2113
Misses 58 58 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Skills files aren't needed now opencode & cursor support them properly
Summary by CodeRabbit
Documentation
Chores
✏️ Tip: You can customize this high-level summary in your review settings.