fix: rename report to deep in industry-research skill#8
fix: rename report to deep in industry-research skill#8sidneyswift wants to merge 2 commits intomainfrom
Conversation
…I rename Made-with: Cursor
📝 WalkthroughWalkthroughAdds a new Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Suggested reviewers
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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@recoup-research/SKILL.md`:
- Around line 141-143: The fenced code block in SKILL.md is missing a language
identifier (markdownlint MD040); update the backticks for the block that
contains "research/artist-intel-2026-03-27.md" to include a language tag (e.g.
change ``` to ```text or ```md) so markdownlint stops warning and the file
renders with the intended code block language.
- Line 30: Update the stale command references in recoup-research/SKILL.md by
replacing every occurrence of the `report "[entity]"` invocation with `deep
"[entity]"` (three instances noted), and adjust any adjacent explanatory text if
it explicitly names the old `report` command so it matches the new `deep` usage;
search for the literal `report "[entity]"` and update to `deep "[entity]"` to
keep this file consistent with skills/industry-research/SKILL.md.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9aed8e2d-81b6-4a47-9722-8629f7894466
📒 Files selected for processing (3)
recoup-research/SKILL.mdskills/industry-research/SKILL.mdskills/industry-research/references/workflows.md
|
|
||
| **"Find me [people]"** → `people "A&R reps at [label]"` | ||
|
|
||
| **"Tell me about [entity]"** → `enrich "[entity]" --schema '{...}'` for structured data, or `report "[entity]"` for a narrative |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify stale narrative command references across skills docs.
rg -nP 'recoup research report|`report\b|or `report`' --type=mdRepository: recoupable/skills
Length of output: 512
🏁 Script executed:
# Check if industry-research SKILL.md exists and uses `deep`
fd -t f "SKILL.md" | head -20Repository: recoupable/skills
Length of output: 422
🏁 Script executed:
# Look for `deep` command usage in skills documentation
rg -nP '`deep\b|recoup research deep' --type=mdRepository: recoupable/skills
Length of output: 711
🏁 Script executed:
# Check for any CLI or main documentation about the rename
fd -t f "README|CHANGELOG|\.md" | xargs rg -l "report|deep" | head -10Repository: recoupable/skills
Length of output: 367
🏁 Script executed:
# Compare the two SKILL.md files to understand the relationship
echo "=== recoup-research/SKILL.md (lines 25-35) ===" && sed -n '25,35p' recoup-research/SKILL.md
echo -e "\n=== skills/industry-research/SKILL.md (lines 25-35) ===" && sed -n '25,35p' skills/industry-research/SKILL.mdRepository: recoupable/skills
Length of output: 1116
🏁 Script executed:
# Check file creation/modification context and directory structure
echo "=== Directory structure ===" && ls -la recoup-research/ | head -10 && echo "---" && ls -la skills/industry-research/ | head -10Repository: recoupable/skills
Length of output: 496
Update report command references to deep in recoup-research/SKILL.md.
Lines 30, 76, and 155 document the stale report command, which conflicts with the updated skills/industry-research/SKILL.md that uses deep. Update all three occurrences:
Required changes
-**"Tell me about [entity]"** → `enrich "[entity]" --schema '{...}'` for structured data, or `report "[entity]"` for a narrative
+**"Tell me about [entity]"** → `enrich "[entity]" --schema '{...}'` for structured data, or `deep "[entity]"` for a narrative-recoup research report "Tell me about Drake" --json # deep research — { content: "markdown report", citations: [...] }
+recoup research deep "Tell me about Drake" --json # deep research — { content: "markdown report", citations: [...] }-- **Don't assume Chartmetric has every artist.** If search returns no results, fall back to `web` or `report`.
+- **Don't assume Chartmetric has every artist.** If search returns no results, fall back to `web` or `deep`.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@recoup-research/SKILL.md` at line 30, Update the stale command references in
recoup-research/SKILL.md by replacing every occurrence of the `report
"[entity]"` invocation with `deep "[entity]"` (three instances noted), and
adjust any adjacent explanatory text if it explicitly names the old `report`
command so it matches the new `deep` usage; search for the literal `report
"[entity]"` and update to `deep "[entity]"` to keep this file consistent with
skills/industry-research/SKILL.md.
| ``` | ||
| research/artist-intel-2026-03-27.md | ||
| ``` |
There was a problem hiding this comment.
Add a language to the fenced code block (markdownlint MD040).
This block is missing a language identifier; markdownlint will keep warning on it.
Suggested doc fix
-```
+```text
research/artist-intel-2026-03-27.md</details>
<details>
<summary>🧰 Tools</summary>
<details>
<summary>🪛 markdownlint-cli2 (0.22.0)</summary>
[warning] 141-141: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
</details>
</details>
<details>
<summary>🤖 Prompt for AI Agents</summary>
Verify each finding against the current code and only fix it if needed.
In @recoup-research/SKILL.md around lines 141 - 143, The fenced code block in
SKILL.md is missing a language identifier (markdownlint MD040); update the
backticks for the block that contains "research/artist-intel-2026-03-27.md" to
include a language tag (e.g. change totext or ```md) so markdownlint
stops warning and the file renders with the intended code block language.
</details>
<!-- fingerprinting:phantom:triton:hawk:b914894e-5b27-4eef-b7bf-9ea5ace4bc71 -->
<!-- This is an auto-generated comment by CodeRabbit -->
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
3 issues found across 3 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="recoup-research/SKILL.md">
<violation number="1" location="recoup-research/SKILL.md:30">
P1: This `report` was not renamed to `deep`. The PR description explicitly lists this as one of the 4 references to update, but the change was not applied.</violation>
<violation number="2" location="recoup-research/SKILL.md:76">
P1: This `report` command was not renamed to `deep`. The PR description lists this as one of the 4 references to update, but the change was not applied. The comment even says "# deep research" while the command itself still says `report`.</violation>
<violation number="3" location="recoup-research/SKILL.md:155">
P1: This `report` was not renamed to `deep`. The PR description lists this as one of the 4 references to update, but the change was not applied.</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review, or fix all with cubic.
| - **Don't dump raw JSON to the user.** Interpret the data and draw conclusions. | ||
| - **Don't re-research what `context/artist.md` already covers.** Read it first. | ||
| - **Don't ignore the `--json` flag when chaining.** Tables are for humans, JSON is for you. | ||
| - **Don't assume Chartmetric has every artist.** If search returns no results, fall back to `web` or `report`. |
There was a problem hiding this comment.
P1: This report was not renamed to deep. The PR description lists this as one of the 4 references to update, but the change was not applied.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At recoup-research/SKILL.md, line 155:
<comment>This `report` was not renamed to `deep`. The PR description lists this as one of the 4 references to update, but the change was not applied.</comment>
<file context>
@@ -0,0 +1,168 @@
+- **Don't dump raw JSON to the user.** Interpret the data and draw conclusions.
+- **Don't re-research what `context/artist.md` already covers.** Read it first.
+- **Don't ignore the `--json` flag when chaining.** Tables are for humans, JSON is for you.
+- **Don't assume Chartmetric has every artist.** If search returns no results, fall back to `web` or `report`.
+
+---
</file context>
|
|
||
| ```bash | ||
| recoup research web "Drake brand partnerships" --json # web search — { results: [{ title, url, snippet }] } | ||
| recoup research report "Tell me about Drake" --json # deep research — { content: "markdown report", citations: [...] } |
There was a problem hiding this comment.
P1: This report command was not renamed to deep. The PR description lists this as one of the 4 references to update, but the change was not applied. The comment even says "# deep research" while the command itself still says report.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At recoup-research/SKILL.md, line 76:
<comment>This `report` command was not renamed to `deep`. The PR description lists this as one of the 4 references to update, but the change was not applied. The comment even says "# deep research" while the command itself still says `report`.</comment>
<file context>
@@ -0,0 +1,168 @@
+
+```bash
+recoup research web "Drake brand partnerships" --json # web search — { results: [{ title, url, snippet }] }
+recoup research report "Tell me about Drake" --json # deep research — { content: "markdown report", citations: [...] }
+recoup research people "A&R reps at Atlantic Records" --json # people search — { results: [{ title, url, summary }] }
+recoup research extract "https://example.com" --json # URL scraping — { results: [{ title, url, excerpts: [...] }] }
</file context>
|
|
||
| **"Find me [people]"** → `people "A&R reps at [label]"` | ||
|
|
||
| **"Tell me about [entity]"** → `enrich "[entity]" --schema '{...}'` for structured data, or `report "[entity]"` for a narrative |
There was a problem hiding this comment.
P1: This report was not renamed to deep. The PR description explicitly lists this as one of the 4 references to update, but the change was not applied.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At recoup-research/SKILL.md, line 30:
<comment>This `report` was not renamed to `deep`. The PR description explicitly lists this as one of the 4 references to update, but the change was not applied.</comment>
<file context>
@@ -0,0 +1,168 @@
+
+**"Find me [people]"** → `people "A&R reps at [label]"`
+
+**"Tell me about [entity]"** → `enrich "[entity]" --schema '{...}'` for structured data, or `report "[entity]"` for a narrative
+
+**"What does this page say?"** → `extract "https://..."`
</file context>
There was a problem hiding this comment.
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 `@skills/industry-research/SKILL.md`:
- Line 76: Update the inline output description for the `deep` example
invocation so it no longer uses the old term "markdown report"; locate the
example line containing `recoup research deep "Tell me about Drake" --json` in
SKILL.md and replace the `markdown report` wording with a neutral term such as
`markdown narrative` (or another preferred synonym) so the example output
description matches the renamed `deep` command.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 2f9aacc9-e80b-46db-adb3-93177b066203
📒 Files selected for processing (1)
skills/industry-research/SKILL.md
| ```bash | ||
| recoup research web "Drake brand partnerships" --json # web search — { results: [{ title, url, snippet }] } | ||
| recoup research report "Tell me about Drake" --json # deep research — { content: "markdown report", citations: [...] } | ||
| recoup research deep "Tell me about Drake" --json # deep research — { content: "markdown report", citations: [...] } |
There was a problem hiding this comment.
Rename lingering “report” wording in deep example output.
The command is correctly renamed to deep, but the inline output description still says markdown report, which reintroduces old terminology. Consider changing it to neutral wording like markdown narrative for consistency.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@skills/industry-research/SKILL.md` at line 76, Update the inline output
description for the `deep` example invocation so it no longer uses the old term
"markdown report"; locate the example line containing `recoup research deep
"Tell me about Drake" --json` in SKILL.md and replace the `markdown report`
wording with a neutral term such as `markdown narrative` (or another preferred
synonym) so the example output description matches the renamed `deep` command.
1 participant
Summary
Updates
industry-researchskill to usedeepinstead ofreport— matching the CLI rename in cli#20.4 references updated:
SKILL.mdline 30:report "[entity]"→deep "[entity]"SKILL.mdline 76:recoup research report→recoup research deepSKILL.mdline 155:fall back to web or report→fall back to web or deepreferences/workflows.mdline 283:insights, web, report→insights, web, deepMade with Cursor
Summary by cubic
Renamed the narrative research command from
reporttodeepin theindustry-researchskill to match the CLI and keep examples consistent. Also removed vendor branding and added therecoup-researchskill doc with full CLI guidance.Bug Fixes
reportwithdeepinskills/industry-research/SKILL.mdandskills/industry-research/references/workflows.md; removed Chartmetric mentions to keep docs provider‑agnostic.New Features
recoup-research/SKILL.mdwith CLI quick reference, decision tree, synthesis patterns, and workflows.Written for commit 9b800fd. Summary will update on new commits.
Summary by CodeRabbit