Article status

Answer one question fast: which per-article writing skills have run on this article, and which haven't. Then offer the review if it's missing. This skill only reads; the only thing it starts is write-review, and only after the user says yes.

Usage

/write:status [article]

article is a path to an index.md or its bundle folder. Omit it to check the last article created or changed (the same lookup write-review uses).

Workflow

1. Resolve the article. If the user named one, use it. If you created or edited an article earlier in this conversation, use the last one. Otherwise run the check with no argument: the script calls write-review/scripts/last-article.sh, which picks the repo from $BLOG_ROOT, else the current directory's git repo if it has content/ or hugo/content/, else ~/Projects/websites/jeffbaileyblog; inside it, the newest uncommitted article wins, then the most-changed article of the last commit. The script prints that choice on its Picked by: line. Repeat it to the user, because from the wrong directory the default repo can silently pick a different article than the one they meant.

2. Run the check. Needs only python3 and git (command -v python3 git; if missing, say "tool missing" and stop).