Hierarchical visualization of developer tasks across code repositories
Project description
tickle ๐ชถ
A lightweight, cross-platform tool that provides hierarchical visualization of TODOs, code comments, and markdown checkboxes across your repositories and personal notes.
The name? It's all about ticking things off your list.
Platform Support: Windows, Linux, macOS
Why?
I wanted a fast, configurable way to surface TODOs across many repos. Whether it's tracking bugs in code or managing your life in markdown journals and task lists, tickle finds and reports what needs attention.
Features
- Hierarchical tree view showing tasks organized by directory structure
- Multi-repo scanning
- Configurable task markers (TODO, FIXME, BUG, NOTE, HACK, CHECKBOX)
- Markdown checkbox detection (finds unchecked
- [ ]items) - Git blame enrichment (shows who wrote each task and when)
- Visual summary panel showing task counts and breakdown
- Alternative JSON / Markdown output formats for automation
- Cross-platform compatibility (Windows, Linux, macOS)
Installation
From PyPI (Recommended)
pip install tickle-cli
From Source (Development)
git clone https://github.com/colinmakerofthings/tickle-cli.git
cd tickle-cli
pip install -e ".[dev]"
Usage
Check the version:
tickle --version
Scan the current directory for tasks:
tickle
Output shows a hierarchical tree view with summary panel:
โโโโโโโโ Task Summary โโโโโโโโโ
โ Total: 14 tasks in 6 files โ
โ BUG: 2 | FIXME: 5 | TODO: 7 โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
๐ tickle-cli (14 tasks)
โโโ ๐ src (10)
โ โโโ ๐ tickle (10)
โ โ โโโ ๐ cli.py (2)
โ โ โ โโโ [TODO] Line 15: Add config file support (by alice, 2 days ago)
โ โ โ โโโ [FIXME] Line 42: Handle edge case (by bob, 3 weeks ago)
โ โ โโโ ๐ scanner.py (3)
โ โ โโโ [BUG] Line 67: Memory leak (by charlie, 1 month ago)
โโโ ๐ tests (4)
โโโ ๐ test_cli.py (4)
Note: Git blame information (author and date) is automatically included when scanning git repositories. Use --no-blame to disable this feature for faster scanning.
Scan a specific directory:
tickle /path/to/repo
Filter by specific task markers:
tickle --markers TODO,FIXME,BUG
Show collapsed tree view (counts only):
tickle --tree-collapse
This shows just the directory structure with task counts, hiding individual task details.
Output in JSON format (for automation):
tickle --format json
Output in Markdown format (for documentation):
tickle --format markdown
Note: Summary panel and tree view are shown by default. Use --format json or --format markdown for machine-readable or documentation output.
Ignore specific file patterns:
tickle --ignore "*.min.js,node_modules,build"
Sort tasks by marker priority:
tickle --sort marker
This groups tasks by priority (BUG โ FIXME โ TODO โ HACK โ NOTE โ CHECKBOX), making it easy to focus on critical issues first. Default is --sort file which sorts by file path and line number.
Sort by commit age (oldest first):
tickle --sort age
This shows oldest TODOs first based on git commit date, helping identify technical debt and long-standing issues. Tasks without git blame data appear last.
Sort by author:
tickle --sort author
This groups tasks alphabetically by author name, making it easy to see who wrote each TODO. Requires git blame to be enabled (default).
Reverse any sort order:
tickle --sort marker --reverse
The --reverse flag inverts any sort order. Use it with --sort file (ZโA paths), --sort marker (lowest to highest priority), --sort age (newest first), or --sort author (ZโA names).
Scan for markdown checkboxes:
tickle --markers CHECKBOX
This finds all unchecked markdown checkboxes (- [ ] or * [ ]) in your markdown files.
Include hidden directories in scan:
tickle --include-hidden
By default, hidden directories (starting with . like .git, .vscode) are ignored. Use this flag to include them.
Disable git blame enrichment:
tickle --no-blame
By default, tickle enriches task output with git blame information (author and date). Use this flag to skip git blame for faster scanning when you don't need author/date information.
Show verbose git information:
tickle --git-verbose
This shows additional git details including the commit hash and commit message for each task. Only works when git blame is enabled (don't use with --no-blame).
Combine options:
ticklะต /path/to/repo --markers TODO,FIXME --ignore "tests,venv" --sort marker --reverse --tree-collapse
Configuration
Tired of typing the same flags every time? Configuration files let you set persistent defaults for ignore patterns, markers, output format, and more. Share configuration across your team via pyproject.toml, or maintain personal preferences in your user config.
Quick Start
Create a configuration file in your project:
tickle init
This creates a tickle.toml file in the current directory with sensible defaults. Edit this file to customize your ignore patterns, markers, and other settings.
View your effective configuration:
tickle config show
This shows which config file is being used and the final merged settings.
Configuration Files
tickle supports multiple configuration file locations with the following precedence (highest to lowest):
- Explicit config (via
--configflag) - Project-level:
tickle.tomlor.tickle.tomlin current directory - pyproject.toml:
[tool.tickle]section inpyproject.toml - User-level:
- Linux/Mac:
~/.config/tickle/tickle.toml - Windows:
%APPDATA%\tickle\tickle.toml
- Linux/Mac:
CLI arguments always take precedence over configuration files.
Minimal Configuration Example
A typical tickle.toml for ignoring common build artifacts:
[tickle]
# Task markers to search for
markers = ["TODO", "FIXME", "BUG", "NOTE", "HACK", "CHECKBOX"]
# Patterns to ignore (glob-style)
ignore = [
"*.min.js",
"*.min.css",
"node_modules",
"dist",
"build",
"__pycache__",
".git"
]
Comprehensive Configuration Example
See tickle.toml.example for a complete example with all available options and comments.
All available configuration options:
[tickle]
# Task markers to search for
markers = ["TODO", "FIXME", "BUG", "NOTE", "HACK", "CHECKBOX"]
# File/directory patterns to ignore
ignore = ["node_modules", "dist", "*.min.js"]
# Default output format: "tree", "json", or "markdown"
format = "tree"
# Default sort method: "file", "marker", "age", or "author"
sort = "file"
# Reverse sort order
reverse = false
# Include hidden directories (starting with .)
include_hidden = false
# Enable git blame enrichment (author, date, commit info)
git_blame = true
# Show verbose git information (full commit hash and message)
git_verbose = false
# Collapse tree view (show only directory structure with counts)
tree_collapse = false
Configuration Options Reference
| Option | Type | Default | Description | CLI Flag |
|---|---|---|---|---|
markers |
list[str] | ["TODO", "FIXME", "BUG", "NOTE", "HACK", "CHECKBOX"] |
Task markers to search for | --markers |
ignore |
list[str] | [] |
File/directory patterns to ignore | --ignore |
format |
str | "tree" |
Output format (tree, json, markdown) |
--format |
sort |
str | "file" |
Sort method (file, marker, age, author) |
--sort |
reverse |
bool | false |
Reverse sort order | --reverse |
include_hidden |
bool | false |
Include hidden directories | --include-hidden |
git_blame |
bool | true |
Enable git blame enrichment | --no-blame (inverted) |
git_verbose |
bool | false |
Show full git commit info | --git-verbose |
tree_collapse |
bool | false |
Show only directory structure | --tree-collapse |
Troubleshooting Configuration
Config not loading?
Use tickle config show to see which config file is being used and verify your settings.
Values not applying?
Remember that CLI arguments always override config file values. If you pass --markers TODO, it will override the markers setting in your config file.
Unknown keys warning?
tickle will warn about unrecognized configuration keys but will continue running. Check your spelling and refer to the options table above.
Real-World Examples
Example 1: Ignore build artifacts in a Node.js project
[tickle]
ignore = [
"node_modules",
"dist",
"build",
"*.min.js",
"*.min.css",
"coverage"
]
Example 2: Focus on critical issues only
[tickle]
markers = ["BUG", "FIXME"]
sort = "marker"
Example 3: Team-shared configuration in pyproject.toml
[tool.tickle]
markers = ["TODO", "FIXME", "BUG", "HACK"]
ignore = ["dist", "build", "__pycache__", "*.egg-info", ".venv"]
sort = "age" # Show oldest TODOs first for tech debt review
git_verbose = true # Show full commit context
Example 4: Fast scanning without git info
[tickle]
git_blame = false # Skip git blame for faster scanning
tree_collapse = true # Show only counts
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file tickle_cli-0.2.0.tar.gz.
File metadata
- Download URL: tickle_cli-0.2.0.tar.gz
- Upload date:
- Size: 43.7 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.2
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
1e22f1ae10b4164257d72b0e1581eb2a5d48251d12cbc1e33e44ab962e5d19bc
|
|
| MD5 |
1577565e5836382692925bd1789cf6a8
|
|
| BLAKE2b-256 |
4e13a9ae7bccb669f9c544ce0ebcd59680965fabd7863947ed33f3c0e2a3bb89
|
File details
Details for the file tickle_cli-0.2.0-py3-none-any.whl.
File metadata
- Download URL: tickle_cli-0.2.0-py3-none-any.whl
- Upload date:
- Size: 24.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.13.2
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
92dabe966f3606049e36232a85ebf235bdaa58d22a02aa06a9637f955aa16ebb
|
|
| MD5 |
9e82604b00b948859ec5a7a425f55f2e
|
|
| BLAKE2b-256 |
8a5fd6a088a3c92f6ecc6f66469c8ef2b2bd5840e10b741314599098e5f3e6f1
|