gitwtfhub

wtf is comprehensive-scripture-search?

lukejoneslj/comprehensive-scripture-search — explained in plain English

Analysis updated 2026-05-18

0PythonAudience · generalComplexity · 2/5Setup · moderate

TL;DR

A search tool that finds the most similar passages across the Book of Mormon, D and C, Pearl of Great Price, both Testaments, and the Quran by meaning, not exact keywords.

Mindmap

Mindmap is still cooking. Refresh in a few.

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Search a topic like forgiveness across all six texts at once.

REASON 2

Look up a specific verse or chapter reference and see similar passages elsewhere.

REASON 3

Try the hosted Hugging Face Space with no installation needed.

REASON 4

Run the search tool locally or in Docker for offline or private use.

What's in the stack?

PythonFlaskDockerQwen3-Embedding

How it stacks up

lukejoneslj/comprehensive-scripture-search0xhassaan/nn-from-scratch3ks/embedoc
Stars00
LanguagePythonPythonPython
Last pushed2023-06-08
MaintenanceDormant
Setup difficultymoderatemoderatehard
Complexity2/54/51/5
Audiencegeneraldeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires Git LFS to pull the large pre-computed embeddings file before the app will run correctly.

The code's own license isn't stated in the README, the scripture text data comes from separate sources that each carry their own license.

Wtf does this do

Comprehensive Scripture Search lets someone search six religious texts at once using meaning based search instead of exact keyword matching. The texts covered are the Book of Mormon, Doctrine and Covenants, Pearl of Great Price, the New Testament, the Old Testament, and the Quran. A user can type a topic or phrase, like "forgiveness of enemies" or "the creation of the world", and the tool returns the passages across all six texts that are closest in meaning, even if those exact words never appear. Under the hood, every verse in all six texts, 48,231 of them in total, has already been converted into a numerical representation called an embedding, using a model called Qwen3-Embedding-0.6B. An embedding captures the meaning of a piece of text as a set of numbers, so texts with similar meaning end up with similar numbers. When someone types a search, their query is converted into the same kind of numbers and compared against every verse to find the closest matches. The tool also supports looking up a specific reference, such as a chapter and verse, and comparing it against passages in the other texts, plus searching at the level of a whole chapter rather than a single verse. There is a hosted version available with no installation required, running as a free Hugging Face Space. To run it locally, the project needs Git LFS installed because the pre-computed embeddings file is large, then a standard pip install and a Python script to start a local Flask server. A Docker option is also provided for anyone who prefers a container based setup. The scripture text itself comes from two separate open source projects, and the README notes that each source carries its own license that should be checked before the text is redistributed elsewhere.

Yoink these prompts

Prompt 1
Help me set up Git LFS and clone this repo so the embeddings file downloads correctly.
Prompt 2
Explain how verse embeddings and cosine similarity are used to power the search in this project.
Prompt 3
Walk me through building and running the Docker image for Comprehensive Scripture Search.
Prompt 4
Help me understand the licensing of the scripture text sources this project depends on.

Frequently asked questions

wtf is comprehensive-scripture-search?

A search tool that finds the most similar passages across the Book of Mormon, D and C, Pearl of Great Price, both Testaments, and the Quran by meaning, not exact keywords.

What language is comprehensive-scripture-search written in?

Mainly Python. The stack also includes Python, Flask, Docker.

What license does comprehensive-scripture-search use?

The code's own license isn't stated in the README, the scripture text data comes from separate sources that each carry their own license.

How hard is comprehensive-scripture-search to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is comprehensive-scripture-search for?

Mainly general.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.