Skip to content

When creating a paper review, make multiple trials when the article files are not readable - #59

Merged
Yann-CV merged 2 commits into
mainfrom
paper-review-retry-unreadable
Oct 14, 2026
Merged

Yann-CV merged 2 commits into
mainfrom
paper-review-retry-unreadable

Conversation

@Yann-CV

@Yann-CV Yann-CV commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Summary by cubic

When a randomly selected paper's full text can't be read, the review now tries another paper instead of stopping immediately. It stops after three unreadable papers and reports what failed for each.

  • Adds a repeatable --exclude option to avoid papers already tried.
  • Papers named by the user are never replaced.

Written for commit bf8660e. Summary will update on new commits.

View guided diff Turn on auto-fix

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

All reported issues were addressed across 2 files

Reply with feedback, questions, or to request a fix.

View guided diff | Turn on auto-fix | Re-trigger cubic

Comment thread skills/paper-review/SKILL.md Resolved
Comment thread skills/paper-review/scripts/papers.py Resolved
…escape quotes in links

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Yann-CV
Yann-CV merged commit dc0173a into main Oct 14, 2026
1 check passed
@Yann-CV
Yann-CV deployed to linkedin-post October 14, 2026 15:57 — with GitHub Actions Active
@Yann-CV
Yann-CV deleted the paper-review-retry-unreadable branch October 14, 2026 16:08
@Yann-CV
Yann-CV deployed to linkedin-post October 15, 2026 15:30 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
linkedin-post — bf8660ed Deployed Oct 15, 2026 by Yann-CV via Publish the post on LinkedIn #3
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