jabref
- 10 skills
- 0 followers
- 9 hours ago last updated
- ▌ Cr Create · jabref bundleDrive an end-to-end GitBook docs review flow from Claude Code by calling the GitBook REST API directly with curl (no CLI) — create a change request, push content (update an existing page AND create a new page), request reviewers, notify Slack, then pull review comments back in, fix them, re-push, and resolve. This is the authoring-side companion to cr-review (the reviewer side over the same API). Use this whenever someone wants to run a "docs review in GitBook" loop from the terminal/agent against the raw API (curl/HTTP), mentions creating a change request via the API, pushing content into a CR, "pull in the latest comments and fix them," requesting review on docs, or showing engineers how to collaborate on GitBook docs from Claude + Slack without a CLI.
- ▌ Cr Review · jabrefReview GitBook change requests from Claude Code by calling the GitBook REST API directly with curl (no CLI) — the reviewer-side companion to cr-create (the authoring side over the same API). Discover the change requests that need review (filter by who opened them, by space, or across a whole org), get the GitBook app link to review the diff, summarize what actually changed in a CR, then leave comments and optionally submit a review verdict (approve / request changes). Use this whenever someone wants to review docs change requests over the raw API (curl/HTTP), asks "what CRs are open / waiting on me / opened by <person>", "show me the change requests in <space>/<org>", "summarize what changed in this CR", "review this change request", "leave a comment on a CR", or "approve / request changes on a CR". For the authoring side (create a CR, push content, request reviewers, fix comments) over the API, use cr-create instead.
- ▌ Write Docs · jabref bundleWrite, author, edit, and format GitBook documentation pages in Git-synced repos, IDEs, or any text editor. Use whenever a task involves creating or editing a GitBook markdown page, writing or updating a README.md or SUMMARY.md, inserting a hint, tab, stepper, card, or other GitBook block, configuring page frontmatter or layout options, setting up variables or expressions, or formatting content for GitBook outside the GitBook UI.
- ▌ Jabkit · jabrefJabRef's Swiss Army knife CLI for BibTeX/biblatex - fetches entries online, converts DOIs to BibTeX, turns PDF papers into BibTeX entries, checks libraries, generates citation keys, writes XMP metadata, and searches .bib files.
- ▌ PDF To Bibtex · jabrefTurns a PDF paper into a BibTeX entry describing that paper, using JabRef's jabkit CLI - merges XMP, embedded BibTeX, GROBID, and text heuristics, then enriches the result via DOI/arXiv/ISBN lookup; builds a bibliography from a whole folder of papers. Not for extracting the reference list cited by a paper.
- ▌ Github Actions · jabrefHow to reference GitHub Actions in JabRef workflows — pin every external action to a full commit SHA with the release tag as a comment, and how to resolve that SHA. Use when adding or editing a `uses:` line under .github/workflows.
- ▌ PDF Extract References · jabrefExtracts the works a paper cites - parses the "References" section of PDF papers with JabRef's jabkit CLI and outputs the cited entries as BibTeX, via offline rule-based parsing (IEEE-style numbered references), a GROBID service, or an experimental LLM mode.
- ▌ Jabref Contributor · jabrefGradle build, module layout (jablib, jabgui, jabkit, jabls, jabsrv), JUnit 5 testing rules, naming conventions, and the mandatory pre-PR checklist for contributing to JabRef.
- ▌ Module Documentation · jabrefHow to write and maintain package-level (package-info.java) and module-level (module-info.java) Javadoc in JabRef, including deep links into devdocs.jabref.org. Use when adding a package or changing a package's or module's public surface.
- ▌ Bibtex Library Management · jabrefValidates, cleans, and repairs BibTeX/biblatex libraries with JabRef's jabkit CLI - integrity checks, citation key generation, searching, format conversion, and pseudonymization before sharing.