<commit_before>Whatnext
========

Whatnext is a lightweight tool to keep you on track. It is a simple shell layer
over the file system designed for use from the command line or in scripts.
Combined with source control, it allows for powerful tracking of what you
should do next.

Usage
-----

```
whatnext [echo]
```
Displays the path of the current task and its contents, if it exists. If there
is no current task, the tasks in the queue will be display. If no tasks are
queued, all open tasks will be displayed.

```
whatnext add <project> <task_name><commit_msg>Improve README<commit_after>Whatnext
========

Whatnext is a lightweight tool to keep you on track. It is a simple shell layer
over the file system designed for use from the command line or in scripts.
Combined with source control, it allows for powerful tracking of what you
should do next.

Each task is a file on your computer. Task requirements, notes, completion
estimates, and deadlines can go there, but `whatnext` doesn't care. These files
are grouped together into folders called projects. Managing a project as a git
repository allows for collaboration and history control beyond most dedicated
task management systems.

Usage
-----

```
whatnext [echo]
```
Displays the path of the current task and its contents, if it exists. If there
is no current task, the tasks in the queue will be display. If no tasks are
queued, all open tasks will be displayed.

```
whatnext add <project> <task_name>
{'fraction_non_alphanumeric': 0.06330837304288632, 'fraction_numerical': 0.0, 'mean_word_length': 4.306859205776173, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3035131', 'n_tokens_mistral': 385, 'n_tokens_neox': 367, 'n_words': 232}