Dwight Ivany118 downloadsFinds notes containing incomplete tasks and writes a dated list of links.
An Obsidian plugin that scans your vault for notes containing incomplete tasks (- [ ]) and writes a dated list of links to a file.
This helps me maintain a system I trust to track action items. I am a fan of David Allen's Getting Things Done. He suggested never mixing action items with reference material. Obsidian makes it really easy to confuse those.
Maybe you have Tasks items in a limited set of Files and Folders, and you trust that you will track those nicely. Set up those to be excluded, like Projects and Daily. Then during your reviews (I like weekly review) click the icon for the plugin and see, if there are actions in other places like Reference folders. I then like to move or action those.
todo-files-YYYY-MM-DD.md to the vault root, containing one [[wikilink]] per note that has at least one unchecked taskDownload main.js and manifest.json from the latest release and copy them into your vault's plugin folder:
<your vault>/.obsidian/plugins/my-task-checker/
Create the my-task-checker folder if it doesn't exist. Then enable the plugin under Settings → Community plugins.
todo-files-YYYY-MM-DD.md in the vault root — each line links to a note with open tasksThe Show task count command reports how many notes contain incomplete tasks without writing a file.
Go to Settings → Task Checker:
Use the list controls to add, reorder, and remove entries. Paths are stored relative to the vault. If you previously saved absolute filesystem paths, they are converted to vault-relative paths when settings load.
Entries are stored in the plugin's data.json.
With Node.js installed:
npm install
npm run build # writes main.js to this folder (repo root)
For development with watch mode:
npm run dev
Lint and typecheck with the same rules the Obsidian plugin review applies:
npm run lint
npm run typecheck
On Windows without Node/npm, use the standalone build script (downloads tools/esbuild.exe on first run):
.\build.ps1
The script builds main.js in the repo root and copies main.js and manifest.json into ../../../.obsidian/plugins/my-task-checker (relative to this folder), ready to reload in Obsidian.
package.json and manifest.json, and add it to versions.json.v prefix):git tag -a 1.3.1 -m "1.3.1"
git push origin 1.3.1
GitHub Actions builds main.js, attests main.js and manifest.json, and publishes those files on the GitHub release. Upload the repository manifest.json unchanged so it matches the release.