Summarize checked and unchecked Markdown tasks
Paste a GFM task list and choose Inspect Markdown. The result counts parsed tasks and lists their status, text and one-based source line. It reads the checkbox state in the document; it does not change that state or infer whether work is actually complete.
Example with a nested task
Load the example and inspect it. There are three tasks: Draft complete is checked, Review content is unchecked, and the nested Check example is checked. The summary is therefore three tasks, two checked and one unchecked. The parent Review content row does not repeat the nested task's text.
What counts as a task
The tool uses remark with GFM task-list parsing. A valid checked or unchecked marker at the start of a list item creates a task. Ordinary list items do not count, nor do checkbox-like characters inside code or prose. Nested tasks count individually even when their parent is unchecked. A checked child does not automatically change the parent.
Task text is a plain-text interpretation of the item's non-list content. Inline formatting markers are removed, and nested lists are omitted from the parent's label. The report preserves source order and repeated task labels. It does not detect assignees, deadlines, priorities, dependencies or completion percentages weighted by effort. Checkbox counts should not be presented as a measured project-progress estimate.
Save a snapshot
The preview contains up to 200 rows. Copy JSON report or Download JSON exports every parsed task with checked or unchecked status. Zero tasks yields an empty report; check that your source uses GFM list syntax if tasks were expected. Input is capped at 50,000 UTF-16 code units, 20,000 syntax nodes and 100 nesting levels. Edits clear the result, and no project state is saved remotely.
Use Markdown Heading Extractor to review the sections containing these tasks, or Markdown Link Extractor to inventory task-related references separately.





