Skip to content

docs: record literature-review tooling research option - #9

Merged
R0SEWT merged 1 commit into
mainfrom
docs/catalog-literature-review
Sep 27, 2026
Merged

R0SEWT merged 1 commit into
mainfrom
docs/catalog-literature-review

Conversation

@R0SEWT

@R0SEWT R0SEWT commented Sep 26, 2026 •

Copy link
Copy Markdown
Owner

Why

Record the tooling research for a verified literature review (with BibTeX for a LaTeX report), done for the PC1 of cursos/concurrente, so the next literature task starts with the known-good tools and the known pitfalls.

Changes

  • catalog/setup-options.md: new entry dated 2026-09-11.
    • Adopt: the claude-scholar plugin as the primary tool (OpenAlex, DOI → BibTeX, check-refs), and direct Crossref/OpenAlex/doi.org calls as the fallback. Crossref finds CS venues better than OpenAlex.
    • Trial: exa for discovering material that isn't indexed.
    • Reject: academic MCP servers, which overlap with the installed tools.
    • Friction noted: the dblp API sits behind a bot check.

No wiring: nothing is added to templates/.

Stacked on #5 (the catalog is newest first, so this entry goes below its 2026-09-24 one). Merge #5 first. Also bumps the plugin to 0.2.1: skills/research-setup/SKILL.md now lists claude-scholar and exa as installed.

Validation

🤖 Generated with Claude Code

Summary by Sourcery

Record the validated tooling choices and operational pitfalls for reproducible literature reviews without adding template wiring.

Enhancements:

  • Document research findings and recommendations for verified literature reviews, including primary, fallback, and discovery tooling plus known API limitations.
  • Update the research setup inventory to include the claude-scholar and exa plugins.

Documentation:

  • Add a dated catalog entry covering literature-review tooling selection, BibTeX generation, verification practices, and rejected alternatives.

Chores:

  • Bump the plugin version to 0.2.1.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Sorry @R0SEWT, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 days and 17 hours by commenting @sourcery-ai review. Upgrade to get a review now.

@sourcery-ai

sourcery-ai Bot commented Sep 26, 2026

Copy link
Copy Markdown

Reviewer's Guide

Adds a dated documentation-only setup option describing the known-good CLI workflow for verified literature reviews with LaTeX BibTeX output, its fallbacks and limitations, and the tools deliberately not adopted; no templates or runtime wiring change.

Flow diagram for the verified literature review tooling workflow

flowchart TD
    Start["Literature review need"] --> Primary["claude-scholar\nOpenAlex, DOI to BibTeX, check-refs"]
    Primary --> Verify["Verify references and LaTeX .bib"]
    Primary --> Thin["Search results look thin"]
    Thin --> Fallback["curl fallback\nCrossref, OpenAlex, doi.org"]
    Fallback --> Verify
    Start --> Discovery["exa\nTrial for non-indexed material"]
    Discovery --> Verify
    Verify --> Report["Verified literature review\nwith BibTeX output"]
Loading

File-Level Changes

Change Details Files
Document the verified literature-review tooling evaluation and selected workflow.
  • Add a dated catalog entry covering requirements and findings from the PC1 review.
  • Recommend the installed claude-scholar plugin for OpenAlex search, DOI-to-BibTeX conversion, and reference checking.
  • Document direct Crossref/OpenAlex/doi.org calls as fallback, including Crossref’s stronger CS-venue discovery and OpenAlex abstract-search limitation.
  • Record exa as a complementary discovery trial and academic MCP servers as rejected due to overlap.
  • Capture dblp’s bot-check friction and explicitly confirm that no template wiring is required.
catalog/setup-options.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Comment thread catalog/setup-options.md

<!-- entries below -->

## 2026-09-11 — tooling for a verified literature review (+ BibTeX for a LaTeX report)

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

PR #5 inserts its entry at the same spot, directly under <!-- entries below -->. git merge-tree of the two branches reports a conflict.

Whichever merges second hits a conflict. The log is documented as "Newest first", so the 2026-09-11 entry has to sit below 2026-09-24. A quick resolution that keeps "theirs on top" (for example, merging #9 after #5) puts the entries out of date order.

Automated review (Claude Code, AI-generated). Validate before acting.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Fixed in 688863d: #9 is now stacked on #5, with this entry below 2026-09-24. Merge #5 first. (Claude Opus 5.5, on behalf of Rody)

Comment thread catalog/setup-options.md Outdated
- Fit: strong. No key, free, and `check-refs` closes the loop against the written report — which
matches the reproducibility value better than a search-only tool.
- Maintenance: installed plugin, in use.
- Verdict: **adopt** — primary tool. Used for the PC1 review in `cursos/concurrente` (issue #5).

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

The bare (issue #5) refers to an issue in cursos/concurrente, but GitHub autolinks it to project-kit#5, the unrelated data-storage PR.

A reader clicking the evidence link lands on the HF/DVC storage PR, so the provenance claim for the "adopt" verdict points at the wrong thing. Use the qualified R0SEWT/<concurrente-repo>#5.

Automated review (Claude Code, AI-generated). Validate before acting.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Fixed in 688863d: R0SEWT/concurrente#5. (Claude Opus 5.5, on behalf of Rody)

Comment thread catalog/setup-options.md
a paper accepted but not yet in a DOI registry), weak for bibliographic metadata.
- **Friction found**: the **dblp API is behind a bot check** (`dblp.org/search/publ/api` returns an
Anubis HTML challenge, HTTP 200). Don't script it; use Crossref for CS-venue coverage instead.
- **Wiring**: none. All adopted pieces are already installed or plain `curl`; nothing to add to

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

The entry records claude-scholar and exa as installed and adopted, but skills/research-setup/SKILL.md "Already installed (don't re-propose / weigh overlap)" is left unchanged. That list still names only superpowers/frontend-design/github-map/playwright/context7.

The next research-setup run doesn't weigh overlap with claude-scholar or exa, and may re-propose the academic MCP servers this entry just rejected for overlapping with them. "Wiring: none" should include that one-line update to the skill.

Automated review (Claude Code, AI-generated). Validate before acting.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

Fixed in 688863d: added to the research-setup list and bumped the plugin to 0.2.1. (Claude Opus 5.5, on behalf of Rody)

@R0SEWT
R0SEWT force-pushed the docs/catalog-literature-review branch 2 times, most recently from 6365624 to 688863d Compare September 27, 2026 04:13
Stacked on the data-storage entry (newest first). The research-setup
skill now lists claude-scholar and exa as installed, so the plugin
goes to 0.2.1. The concurrente issue link is repo-qualified, and exa
is marked optional under the no-paid-API constraint.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@R0SEWT
R0SEWT force-pushed the docs/catalog-literature-review branch from 688863d to 0a05eb2 Compare September 27, 2026 04:20
@R0SEWT
R0SEWT merged commit dcaa197 into main Sep 27, 2026
3 checks passed
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