Checklist Flow

approved

by oisngodr

Move completed checklist items down and drag-reorder checklist items inside the editor. - This plugin has not been manually reviewed by Obsidian staff.

★ 1 stars↓ 25 downloadsUpdated 8d agoMIT
Install in ObsidianView on GitHub

Checklist Flow

Checklist Flow is an Obsidian plugin for making Markdown task lists feel closer to Apple Notes:

  • Checked tasks automatically sink below unfinished sibling tasks.
  • Ordered task lists keep their starting number after automatic sinking or manual reordering.
  • Same-level task items can be reordered by holding and dragging the task checkbox.

Usage

Install or enable the Checklist Flow plugin in Obsidian, then use normal Markdown task lists:

5. [ ] Listen to a course
6. [ ] Review wrong questions
7. [x] Rest

When a task is checked, completed items move to the bottom of the same contiguous, same-level checklist. Child lines stay attached to their parent task.

To reorder manually, hold the checkbox and drag. An insertion line shows where the task will be placed. A plain click on the checkbox still toggles the task as usual.

Settings

Open Settings > Community plugins > Checklist Flow.

  • Auto-sink completed tasks: move completed tasks below unfinished siblings.
  • Drag from checkbox: hold and drag a task checkbox to reorder same-level items.
  • Done status characters: checkbox states treated as done. Default: xX.

Scope

The plugin intentionally keeps v1 narrow:

  • Works on regular Markdown task lines such as - [ ], - [x], 5. [ ], and 5. [x].
  • Reorders only within the same contiguous checklist and indentation level.
  • Keeps child task blocks and indented notes attached to their parent task.
  • Does not reorder Tasks query results, reading view output, tables, Kanban cards, callouts, or code blocks.

Development

Install dependencies:

npm install --no-audit --no-fund

Run tests:

npm test

Type-check:

npx tsc --noEmit

Build for Obsidian:

npm run build

The build writes main.js, manifest.json, and styles.css in the repository root. Copy those three files into an Obsidian plugin folder named checklist-flow, or install the plugin through your preferred Obsidian plugin development workflow.

For a release, run the test, type-check, and production build commands, then publish the generated main.js, manifest.json, and styles.css as GitHub Release assets. The release tag must match the version in manifest.json; the current maintenance release is 0.1.1.

License

MIT

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.