virgiliojr94/book-to-skill - Open Source PR Review Scorecard

Turn any technical book PDF into a Claude Code skill — ready to study, reference, and use while you work.

C-Rank Grade: A (Welcoming) - 65/100

External PR Merge Rate: 64%

Response Time: 7h

First Timer Success: 82%

Frequently Asked Questions

Is virgiliojr94/book-to-skill welcoming to first-time open-source contributors?

virgiliojr94/book-to-skill has a recorded first-timer success rate of 81.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in virgiliojr94/book-to-skill respond to incoming external pull requests in approximately 7.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 64.8 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 64.8 places virgiliojr94/book-to-skill in the A tier.

What is the external contributor pull request merge rate for virgiliojr94/book-to-skill?

The external contributor pull request merge rate for virgiliojr94/book-to-skill is 63.6%, based on public PR activity from non-core contributors.

Are there Good First Issues available in virgiliojr94/book-to-skill?

virgiliojr94/book-to-skill currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

virgiliojr94
virgiliojr94/book-to-skillA•Welcoming34.3k
GitHub
Back to Explorer
virgiliojr94

virgiliojr94/book-to-skill

34,314
Active (30d)A•Welcoming(65/100)Python

Turn any technical book PDF into a Claude Code skill — ready to study, reference, and use while you work.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.4/10
Patience Score
8.4/10
Nitpick Rate
45%

Highly welcoming maintainers in virgiliojr94/book-to-skill. Prompt code reviews with positive guidance for new contributors.

What Contributors Actually Say

Discussions in virgiliojr94/book-to-skill focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.

Hidden Friction Signals

Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.

Unwritten Rules

  • •1) Keep PR scope strictly aligned with the linked issue.
  • •2) Ensure local linters pass before opening a review.
  • •3) Maintain full test coverage for modified logic.

Top PR Submission Do's

  • •Add or update tests for changed behavior before requesting review
  • •Update docs or README when behavior changes
  • •Link the issue and include reproduction context in the PR

Top PR Friction Pitfalls (Don'ts)

  • •Do not leave requested test coverage unresolved
  • •Do not ship user-facing changes without matching docs
  • •Do not open context-free PRs
Response Velocity
6 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
63.6%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
81.8%
Strong first-timer PR acceptance rate

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
22 core
Highly collaborative maintainer core
Diagnostic Health HUD
63.6%
Merge Gauge
81.8%
1st-Timer
Community Vibe75/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for virgiliojr94/book-to-skill
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/virgiliojr94/book-to-skill)](https://getmerged.abhishekco.de/virgiliojr94/book-to-skill?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

What happened The BeautifulSoup text conversion inserts a newline between every text node, including nodes separated only by inline styling. A span inside a heading, word, or syntax-highlighted code block changes the extracted content. This affects two current paths with the same cause: HTML: the bs4 fallback when Trafilatura is unavailable or does not return usable content. EPUB: the preferred ebooklib + bs4 parser. This path does not use Trafilatura. On unmodified master, a synthetic two-chapter source using Chapter <span>1</span> produces 0 detected chapters. Removing only the span markup produces 2. The styled source still exits successfully through the full CLI, including HTML --mode technical. For code, this source: <pre><code>if enabled: <span>print</span>("ok") </code></pre> becomes: if enabled: print ("ok") Compiling that extracted snippet raises IndentationError; the same snippet without the styling spans, and the current stdlib output for this fixture, compile su

📅 Opened Oct 1, 2026💬 1 comment
Quality: 45/100Contribute

What happened reuse_is_safe() returns (True, "workdir intact and all sources match the current inputs") when the extraction corpus has been deleted, emptied, or replaced with unrelated content. The original input file and its recorded SHA-256 are unchanged in all three cases. Step 0 names this helper as the executable form of the interrupted-run recovery check. Its result can therefore authorize reuse of a missing or corrupted full_text.txt, even though later generation steps read that file. This is a follow-up to the merged source-fingerprint protection in #224: the original-source check works, but it does not establish the integrity of the extraction output. I am not claiming that an actual host agent resumed and generated a wrong skill in this reproduction; the reproduced failure is the helper's incorrect safety verdict. What you expected Unchanged inputs are necessary for reuse, but the extracted corpus must also exist, be readable, and match the completed extraction. Missing or ch

📅 Opened Sep 30, 2026💬 1 comment
Quality: 65/100Contribute

Problem book_to_skill/sanitize.py::is_invisible_codepoint() (sanitize.py:121) is an enumerated blocklist organised by attack shape into eight commented groups. Group 1 already strips U+180E MONGOLIAN VOWEL SEPARATOR (sanitize.py:17) — but the free variation selectors in the same Mongolian block, and two further Default_Ignorable channels, are not in the list. They pass through extraction untouched, and because tools/scan_generated_skill.py imports the same predicate (scan_generated_skill.py:25, consumed by _is_invisible at 113 and the unicode.invisible finding at 241-251), the scanner does not flag them either. That is the exact failure the module documents and exists to prevent (sanitize.py:124-126): Exposed so the generated-skill scanner can flag exactly what extraction strips. When the two sets drift, the extractor lets a character through that the scanner then warns about — or worse, neither layer covers it. The gap, measured is_invisible_codepoint() returns False for nine as

📅 Opened Sep 22, 2026💬 5 comments
Quality: 65/100Contribute

Problem book_to_skill/utils.py::_structural_chapter_count() decides a chapter count by returning len(levels[depth]) for the shallowest heading depth that has at least two distinct titles (utils.py:509). It has no concept of front matter or back matter, so every framing heading at that depth is counted as a teaching chapter. Measured on upstream/master (526f362, v1.4.0) with a synthetic fixture (no copyrighted text) shaped like a real book — 20 titled chapters plus the front matter and back matter a book actually carries: headings role ## Preface, ## Acknowledgements, ## Table of Contents front matter ## Chapter Title 1 … ## Chapter Title 20 the 20 real chapters ## Appendix A: Notation, ## Appendix B: Datasets, ## Glossary, ## Bibliography, ## Index back matter $ python3 scripts/extract.py synthetic-book.md --mode text --install-missing no chapters: 28 (structural) Extraction complete: Chapters: 28 detected overall (structural) ToC : yes metadata.json fro

📅 Opened Sep 20, 2026💬 5 comments
Quality: 35/100Contribute

Problem python3 -m pytest tests/ -q in CI always reports 5 skipped, because the only thing CI installs is pytest (ci.yml:28) and ruff (ci.yml:41). Those 5 tests are gated by pytest.importorskip: Site Dep tests/test_html_block_boundaries.py:131 bs4 tests/test_html_boilerplate_extraction.py:32, 38, 47, 56 trafilatura The consequence is that production fallback behaviour is asserted nowhere in CI — the very behaviour those tests exist to pin. Measured (Ubuntu 20.04, Python 3.9.5, same tree, same interpreter otherwise) pytest tests/ -q -> 698 passed, 5 skipped (ci.yml today: pytest only) pytest tests/ -q (bs4 + trafilatura) -> 703 passed, 0 skipped The skip is purely dependency-gated, proven by flipping one dep at a time: bs4 present, trafilatura absent -> TestConvergenceWithBeautifulSoup 1 passed test_html_boilerplate_extraction 1 passed, 4 skipped trafilatura present, bs4 absent -> test_html_boilerplate_ex

📅 Opened Sep 19, 2026💬 2 comments
Quality: 65/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for virgiliojr94/book-to-skill

When evaluating whether to contribute to virgiliojr94/book-to-skill, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of virgiliojr94/book-to-skill acknowledge new external contributions in approximately 6 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.6% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to virgiliojr94/book-to-skill

01

Is virgiliojr94/book-to-skill welcoming to first-time open-source contributors?

virgiliojr94/book-to-skill has a recorded first-timer success rate of 81.8%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~6 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 64.8 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 64.8 places virgiliojr94/book-to-skill in the Welcoming tier.

04

What is the external contributor pull request merge rate for virgiliojr94/book-to-skill?

The external pull request merge rate is 63.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in virgiliojr94/book-to-skill?

Yes, virgiliojr94/book-to-skill currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for virgiliojr94/book-to-skill are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.