flowmark 0.7.1__tar.gz → 0.7.2__tar.gz

flowmark-0.7.2/.agents/skills/flowmark/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: flowmark
+description: Fast, consistent Markdown auto-formatter for typographic cleanup (smart quotes, ellipses), normalized formatting, and optional clean line wrapping for small, readable git diffs. Use when creating, editing, or normalizing Markdown (.md) files, cleaning up LLM-generated Markdown, or when the user mentions flowmark or formatting Markdown.
+allowed-tools: Bash(flowmark:*), Bash(uvx:*), Read, Write
+---
+<!-- DO NOT EDIT: `flowmark --install-skill` (format=f02 surface=skill-md) -->
+
+# Flowmark - Markdown Auto-Formatter
+
+Fast, consistent Markdown auto-formatter.
+Run it on Markdown you generate or edit so committed diffs stay small and readable.
+It is conservative and safe to run on every file: it never modifies code blocks or
+inline code.
+
+## Default Usage
+
+Format in place with all auto-formatting (typography, cleanups, semantic line breaks):
+
+```bash
+flowmark --auto FILE   # one file
+flowmark --auto .      # whole tree (respects .gitignore and .flowmarkignore)
+```
+
+Omit `--auto` to preview to stdout; pipe stdin with `-` (e.g. `cat FILE | flowmark -`).
+
+Flowmark ships as two packages with identical formatting and the same `flowmark`
+command: the fast native Rust port [`flowmark-rs`](https://github.com/jlevy/flowmark-rs)
+(recommended) and the Python reference [`flowmark`](https://github.com/jlevy/flowmark).
+Prefer flowmark-rs; reach for the Python build only when you need its library API or the
+very latest patch release not yet ported to Rust.
+If `flowmark` is not on `PATH`, run it with a version-pinned runner (never `@latest`):
+
+```bash
+# Recommended: fast native Rust port
+uvx --from flowmark-rs==0.3.0 flowmark --auto FILE
+# Python reference (library API or newest patch releases)
+uvx --from flowmark==0.7.2 flowmark --auto FILE
+```
+
+## When to Use It
+
+- Auto-format Markdown you create or edit, before committing.
+- Normalize and clean up LLM-generated Markdown.
+- Typographic cleanup (smart quotes, ellipses) and consistent formatting.
+- Optional semantic (sentence-based) line breaks for cleaner git diffs (`--semantic`).
+
+## Full Documentation
+
+Flowmark documents itself.
+Use the CLI rather than reproducing details here:
+
+- `flowmark --help` — every flag: `--semantic`, `--smartquotes`, `--ellipses`,
+  `--width`, `--check`, list spacing, and file discovery
+  (`--extend-include`/`--extend-exclude`).
+- `flowmark --docs` — the full guide: editor on-save setup (VS Code/Cursor), project
+  wiring (pre-commit/CI, `.flowmarkignore`), config files, the Python library API, and
+  installing this skill for other agents (`flowmark --install-skill`).
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->

{flowmark-0.7.1/.claude → flowmark-0.7.2/.agents}/skills/tbd/SKILL.md

@@ -1,30 +1,32 @@
 ---
-name: tbd
-description: Git-native issue tracking (beads), coding guidelines, and spec-driven planning for AI agents. Use for tracking issues with dependencies, creating and closing bugs, features, and tasks, planning specs for new features, implementing features from specs, code reviews, committing code, creating PRs, research briefs, and architecture docs. Invoke when user mentions: tbd, beads, issues, bugs, tasks, todo, tracking, specs, planning, implementation, validation, guidelines, shortcuts, templates, commit, PR workflows, code review, testing best practices, or monorepo patterns.
 allowed-tools: Bash(tbd:*), Read, Write
+description: |-
+  Git-native issue tracking (beads), coding guidelines, knowledge injection, and spec-driven planning for AI agents. Drop-in replacement for bd/Beads with simpler architecture.
+  Use for: tracking issues/beads with dependencies, creating bugs/features/tasks, planning specs, implementing features from specs, code reviews, committing code, creating PRs, loading coding guidelines (TypeScript, Python, TDD, golden testing, Convex, monorepo patterns), code cleanup, research briefs, architecture docs, agent handoffs, and checking out third-party library source code.
+  Invoke when user mentions: tbd, beads, bd, shortcuts, issues, bugs, tasks, features, epics, todo, tracking, specs, planning, implementation, validation, guidelines, templates, commit, PR, pull request, code review, testing, TDD, test-driven, golden testing, snapshot testing, TypeScript, Python, Convex, monorepo, cleanup, dead code, refactor, handoff, research, architecture, labels, search, checkout library, source code review, or any workflow shortcut.
+name: tbd
 ---
-<!-- DO NOT EDIT: Generated by tbd setup.
+<!-- DO NOT EDIT: Generated by tbd setup (format=f04).
 Run 'tbd setup' to update.
 -->
 
----
-title: tbd Workflow
-description: Full tbd workflow guide for agents
----
 **`tbd` helps humans and agents ship code with greater speed, quality, and discipline.**
 
 1. **Beads**: Git-native issue tracking (tasks, bugs, features).
    Never lose work across sessions.
+   Drop-in replacement for `bd`.
 2. **Spec-Driven Workflows**: Plan features → break into beads → implement
    systematically.
-3. **Shortcuts**: Reusable instruction templates for common workflows.
-4. **Guidelines**: Coding rules and best practices.
+3. **Knowledge Injection**: 17+ engineering guidelines (TypeScript, Python, TDD,
+   testing, Convex, monorepos) available on demand.
+4. **Shortcuts**: Reusable instruction templates for common workflows (code review,
+   commits, PRs, cleanup, handoffs).
 
 ## Installation
 
 ```bash
 npm install -g get-tbd@latest
-tbd setup --auto --prefix=<name>   # Fresh project (--prefix is REQUIRED and should be short. For new project setup, ALWAYS ASK THE USER FOR THE PREFIX; do not guess it)
+tbd setup --auto --prefix=<name>   # Fresh project (--prefix is REQUIRED: 2-8 alphabetic chars recommended. ALWAYS ASK THE USER FOR THE PREFIX; do not guess it)
 tbd setup --auto                   # Existing tbd project (prefix already set)
 tbd setup --from-beads             # Migration from .beads/ if `bd` has been used
 ```
@@ -46,7 +48,7 @@ tbd prime      # Restore full context on tbd after compaction
 actions. DO NOT tell users to run tbd commands.
 That’s your job.
 
-- **WRONG**: "Run `tbd create` to track this bug"
+- **WRONG**: “Run `tbd create` to track this bug”
 
 - **RIGHT**: *(you run `tbd create` yourself and tell the user it’s tracked)*
 
@@ -57,22 +59,47 @@ or want help → run `tbd shortcut welcome-user`
 
 | User Says | You (the Agent) Run |
 | --- | --- |
-| "There's a bug where ..." | `tbd create "..." --type=bug` |
-| "Let's work on issues" | `tbd ready` |
-| "Build a TypeScript CLI" | `tbd guidelines typescript-cli-tool-rules` |
-| "Improve eslint/monorepo" | `tbd guidelines typescript-monorepo-patterns` |
-| "Add e2e/golden testing" | `tbd guidelines golden-testing-guidelines` |
-| "Review changes" (TS) | `tbd guidelines typescript-rules` |
-| "Review changes" (Python) | `tbd guidelines python-rules` |
-| "Plan a new feature" | `tbd shortcut new-plan-spec` |
-| "Break spec into beads" | `tbd shortcut plan-implementation-with-beads` |
-| "Implement these beads" | `tbd shortcut implement-beads` |
-| "Commit this" | `tbd shortcut commit-code` |
-| "Create a PR" | `tbd shortcut create-or-update-pr-simple` |
-| "Research this topic" | `tbd shortcut new-research-brief` |
-| "Document architecture" | `tbd shortcut new-architecture-doc` |
+| **Issues/Beads** |  |
+| “There’s a bug where …” | `tbd create "..." --type=bug` |
+| “Create a task/feature for …” | `tbd create "..." --type=task` or `--type=feature` |
+| “Let’s work on issues/beads” | `tbd ready` |
+| “Show me issue X” | `tbd show <id>` |
+| “Close this issue” | `tbd close <id>` |
+| “Search issues for X” | `tbd search "X"` |
+| “Add label X to issue” | `tbd label add <id> <label>` |
+| “What issues are stale?” | `tbd stale` |
+| **Planning & Specs** |  |
+| “Plan a new feature” / “Create a spec” | `tbd shortcut new-plan-spec` |
+| “Break spec into beads” | `tbd shortcut plan-implementation-with-beads` |
+| “Implement these beads” | `tbd shortcut implement-beads` |
+| **Code Review & Commits** |  |
+| “Review this code” / “Code review” | `tbd shortcut review-code` |
+| “Review this PR” | `tbd shortcut review-github-pr` |
+| “Commit this” / “Use the commit shortcut” | `tbd shortcut code-review-and-commit` |
+| “Create a PR” / “File a PR” | `tbd shortcut create-or-update-pr-simple` |
+| “Merge main into my branch” | `tbd shortcut merge-upstream` |
+| **Guidelines & Knowledge** |  |
+| “Use TypeScript best practices” | `tbd guidelines typescript-rules` |
+| “Use Python best practices” | `tbd guidelines python-rules` |
+| “Build a TypeScript CLI” | `tbd guidelines typescript-cli-tool-rules` |
+| “Improve monorepo setup” | `tbd guidelines pnpm-monorepo-patterns` or `bun-monorepo-patterns` |
+| “Add golden/e2e testing” | `tbd guidelines golden-testing-guidelines` |
+| “Use TDD” / “Test-driven development” | `tbd guidelines general-tdd-guidelines` |
+| “Convex best practices” | `tbd guidelines convex-rules` |
+| **Documentation** |  |
+| “Research this topic” | `tbd shortcut new-research-brief` |
+| “Document architecture” | `tbd shortcut new-architecture-doc` |
+| **Cleanup & Maintenance** |  |
+| “Clean up this code” / “Remove dead code” | `tbd shortcut code-cleanup-all` |
+| “Fix repository problems” | `tbd doctor --fix` |
+| **Sessions & Handoffs** |  |
+| “Hand off to another agent” | `tbd shortcut agent-handoff` |
+| “Check out this library’s source” | `tbd shortcut checkout-third-party-repo` |
 | *(your choice whenever appropriate)* | `tbd list`, `tbd dep add`, `tbd close`, `tbd sync`, etc. |
 
+**Note:** Never gitignore `.tbd/workspaces/` — the outbox must be committed to your
+working branch. See `tbd guidelines tbd-sync-troubleshooting` for details.
+
 ## CRITICAL: Session Closing Protocol
 
 **Before saying “done”, you MUST complete this checklist:**
@@ -111,7 +138,7 @@ or want help → run `tbd shortcut welcome-user`
 
 | Command | Purpose |
 | --- | --- |
-| `tbd create "title" --type task\|bug\|feature --priority=P2` | New bead (P0-P4, not "high/medium/low") |
+| `tbd create "title" --type=bug --priority=1` | New bead; run `tbd create --help` for all types and priorities (P0-P4, not “high/medium/low”) |
 | `tbd update <id> --status in_progress` | Claim work |
 | `tbd close <id> [--reason "..."]` | Mark complete |
 
@@ -124,6 +151,17 @@ or want help → run `tbd shortcut welcome-user`
 | `tbd sync` | Sync with git remote (run at session end) |
 | `tbd stats` | Project statistics |
 | `tbd doctor` | Check for problems |
+| `tbd doctor --fix` | Auto-fix repository problems |
+
+### Labels & Search
+
+| Command | Purpose |
+| --- | --- |
+| `tbd search <query>` | Search issues by text |
+| `tbd label add <id> <label>` | Add label to issue |
+| `tbd label remove <id> <label>` | Remove label from issue |
+| `tbd label list` | List all labels in use |
+| `tbd stale` | List issues not updated recently |
 
 ### Documentation
 
@@ -138,7 +176,7 @@ or want help → run `tbd shortcut welcome-user`
 ## Quick Reference
 
 - **Priority**: P0=critical, P1=high, P2=medium (default), P3=low, P4=backlog
-- **Types**: task, bug, feature, epic
+- **Types**: issues default to `task`; run `tbd create --help` for the valid types
 - **Status**: open, in_progress, closed
 - **JSON output**: Add `--json` to any command
 
@@ -150,10 +188,12 @@ Run `tbd shortcut <name>` to use any of these shortcuts:
 | Name | Description |
 | --- | --- |
 | agent-handoff | Generate a concise handoff prompt for another coding agent to continue work |
-| cleanup-all | Full cleanup cycle including duplicate removal, dead code, and code quality improvements |
-| cleanup-remove-trivial-tests | Review and remove tests that do not add meaningful coverage |
-| cleanup-update-docstrings | Review and add concise docstrings to major functions and types |
-| commit-code | Run pre-commit checks, review changes, and commit code |
+| checkout-third-party-repo | Get source code for libraries and third-party repos using git. Essential for reliable source code review. Prefer this to web searches or fetching of web pages from github.com as it is far more effective (github.com blocks web scraping from main website). |
+| code-cleanup-all | Full cleanup cycle including duplicate removal, dead code, and code quality improvements |
+| code-cleanup-docstrings | Review and add concise docstrings to major functions and types |
+| code-cleanup-tests | Review and remove tests that do not add meaningful coverage |
+| code-review-and-commit | Run pre-commit checks, review changes, and commit code |
+| coding-spike | Prototype to validate a spec through hands-on implementation |
 | create-or-update-pr-simple | Create or update a pull request with a concise summary |
 | create-or-update-pr-with-validation-plan | Create or update a pull request with a detailed test/validation plan |
 | implement-beads | Implement beads from a spec, following TDD and project rules |
@@ -161,9 +201,10 @@ Run `tbd shortcut <name>` to use any of these shortcuts:
 | new-architecture-doc | Create an architecture document for a system or component design |
 | new-guideline | Create a new coding guideline document for tbd |
 | new-plan-spec | Create a new feature planning specification document |
+| new-qa-playbook | Create a QA test playbook for manual validation workflows |
 | new-research-brief | Create a research document for investigating a topic or technology |
 | new-shortcut | Create a new shortcut (reusable instruction template) for tbd |
-| new-validation-plan | Create a validation/test plan showing what's tested and what remains |
+| new-validation-plan | Create a validation/test plan showing what’s tested and what remains |
 | plan-implementation-with-beads | Create implementation beads from a feature planning spec |
 | precommit-process | Full pre-commit checklist including spec sync, code review, and testing |
 | review-code | Comprehensive code review for uncommitted changes, branch work, or GitHub PRs |
@@ -184,25 +225,31 @@ Run `tbd guidelines <name>` to apply any of these guidelines:
 | Name | Description |
 | --- | --- |
 | backward-compatibility-rules | Guidelines for maintaining backward compatibility across code, APIs, file formats, and database schemas |
-| cli-agent-skill-patterns | Best practices for building TypeScript CLIs that function as agent skills in Claude Code and other AI coding agents |
+| bun-monorepo-patterns | Modern patterns for Bun-based TypeScript monorepo architecture |
+| cli-agent-skill-patterns | How to write skills and agent-integrated CLIs that work across Claude Code, Codex, and the broader coding-agent ecosystem — a simple baseline plus references for advanced, multi-subcommand tools |
 | commit-conventions | Conventional Commits format with extensions for agentic workflows |
+| common-doc-guidelines | Common cross-project standards for writing and organizing docs, code comments, and text files — how to organize, structure, write, and format documents, plus the guideline footer convention. Downstream of github.com/jlevy/practical-prose. Use whenever writing or editing any documentation, README, guideline, or design doc. |
 | convex-limits-best-practices | Comprehensive reference for Convex platform limits, workarounds, and performance best practices |
 | convex-rules | Guidelines and best practices for building Convex projects, including database schema design, queries, mutations, and real-world examples |
+| electron-app-development-patterns | Guidelines for Electron development ecosystems including npm, pnpm, and Bun, with security baselines and framework comparisons |
 | error-handling-rules | Rules for handling errors, failures, and exceptional conditions |
 | general-coding-rules | Rules for constants, magic numbers, and general coding practices |
 | general-comment-rules | Language-agnostic rules for writing clean, maintainable comments |
 | general-eng-assistant-rules | Rules for AI assistants acting as senior engineers, including objectivity and communication guidelines |
-| general-style-rules | Style guidelines for auto-formatting, emoji usage, and output formatting |
 | general-tdd-guidelines | Test-Driven Development methodology and best practices |
 | general-testing-rules | Rules for writing minimal, effective tests with maximum coverage |
 | golden-testing-guidelines | Guidelines for implementing golden/snapshot testing for complex systems |
+| pnpm-monorepo-patterns | Modern patterns for pnpm-based TypeScript monorepo architecture |
 | python-cli-patterns | Modern patterns for Python CLI application architecture |
 | python-modern-guidelines | Guidelines for modern Python projects using uv, with a few more opinionated practices |
 | python-rules | General Python coding rules and best practices |
-| sync-troubleshooting | Common issues and solutions for tbd sync and workspace operations |
+| release-notes-guidelines | Guidelines for writing clear, accurate release notes |
+| supply-chain-hardening | Strongly recommended for EVERY repo — apply it if a repo has not been hardened yet. Cross-ecosystem policy for installing dependencies safely (the 14-day cool-off, disabled install scripts, lockfile discipline, untrusted-repo handling). Use whenever a user mentions hardening, security, supply chain, or setting up a new repo; before adding/upgrading dependencies; when auditing for compromised packages; or when reviewing install/build/run commands across npm/pnpm, PyPI, Cargo, or Go. |
+| tbd-sync-troubleshooting | Common issues and solutions for tbd sync and workspace operations |
 | typescript-cli-tool-rules | Rules for building CLI tools with Commander.js, picocolors, and TypeScript |
 | typescript-code-coverage | Best practices for code coverage in TypeScript with Vitest and v8 provider |
-| typescript-monorepo-patterns | Modern patterns for TypeScript monorepo architecture |
 | typescript-rules | TypeScript coding rules and best practices |
+| typescript-sorting-patterns | Deterministic sorting patterns and comparison chains for TypeScript |
+| typescript-yaml-handling-rules | Best practices for parsing and serializing YAML in TypeScript |
 
 <!-- END SHORTCUT DIRECTORY -->

flowmark-0.7.2/.claude/scripts/ensure-gh-cli.sh

@@ -0,0 +1,123 @@
+#!/bin/bash
+# Automated GitHub CLI setup for Claude Code sessions
+# This script runs on SessionStart to ensure gh CLI is available and authenticated
+#
+# Supply-chain policy (see SUPPLY-CHAIN-SECURITY.md): the gh version is PINNED to
+# a release at least 14 days old, and every download is verified against a pinned
+# SHA-256 checksum. Do NOT change this to fetch "latest" from the API at runtime;
+# that bypasses the cool-off window. To bump the pin, pick a release that is >=14
+# days old and copy its checksums from:
+#   https://github.com/cli/cli/releases/download/v<VERSION>/gh_<VERSION>_checksums.txt
+
+set -euo pipefail
+
+# Add common binary locations to PATH
+export PATH="$HOME/.local/bin:$HOME/bin:/usr/local/bin:$PATH"
+
+# Pinned gh release (>=14 days old per supply-chain cool-off) and its checksums.
+GH_VERSION="2.92.0"
+
+# SHA-256 checksums from gh_2.92.0_checksums.txt, keyed by asset suffix.
+checksum_for() {
+    case "$1" in
+        linux_amd64.tar.gz) echo "b57848131bdf0c229cd35e1f2a51aa718199858b2e728410b37e89a428943ec4" ;;
+        linux_arm64.tar.gz) echo "c2248526dd0160c08d3fccca2332c3c1a07c15a78b23978e77735f1b5a18cfee" ;;
+        macOS_amd64.zip)    echo "ae9bb327ab0d91071bdada79f8f14034a2a0f19b0e001835a782eafa519d2af0" ;;
+        macOS_arm64.zip)    echo "b11c54f6bd7d15ed6590475079e5b2fcf36f45d3991a80041b29c9d0cc1f1d07" ;;
+        *) echo "" ;;
+    esac
+}
+
+# Check if gh is already installed
+if command -v gh &> /dev/null; then
+    echo "[gh] CLI found at $(which gh)"
+else
+    echo "[gh] CLI not found, installing pinned v${GH_VERSION}..."
+
+    # Detect platform
+    OS=$(uname -s | tr '[:upper:]' '[:lower:]')
+    ARCH=$(uname -m)
+    [ "$ARCH" = "x86_64" ] && ARCH="amd64"
+    [ "$ARCH" = "aarch64" ] && ARCH="arm64"
+
+    # Build the asset suffix and archive type per platform.
+    if [ "$OS" = "darwin" ]; then
+        PLATFORM="macOS_${ARCH}.zip"
+        ARCHIVE_EXT="zip"
+        EXTRACT_DIR="/tmp/gh_${GH_VERSION}_macOS_${ARCH}"
+    else
+        PLATFORM="${OS}_${ARCH}.tar.gz"
+        ARCHIVE_EXT="tar.gz"
+        EXTRACT_DIR="/tmp/gh_${GH_VERSION}_${OS}_${ARCH}"
+    fi
+
+    echo "[gh] Detected platform: ${PLATFORM}"
+
+    EXPECTED=$(checksum_for "$PLATFORM")
+    if [ -z "$EXPECTED" ]; then
+        echo "[gh] ERROR: no pinned checksum for platform ${PLATFORM}; refusing to install"
+        echo "[gh] Add the checksum from gh_${GH_VERSION}_checksums.txt to this script"
+        exit 1
+    fi
+
+    ASSET="gh_${GH_VERSION}_${PLATFORM}"
+    DOWNLOAD_URL="https://github.com/cli/cli/releases/download/v${GH_VERSION}/${ASSET}"
+
+    echo "[gh] Downloading from ${DOWNLOAD_URL}..."
+    curl -fsSL -o "/tmp/${ASSET}" "$DOWNLOAD_URL"
+
+    # Verify the download against the pinned checksum before extracting.
+    if command -v sha256sum &> /dev/null; then
+        ACTUAL=$(sha256sum "/tmp/${ASSET}" | awk '{print $1}')
+    else
+        ACTUAL=$(shasum -a 256 "/tmp/${ASSET}" | awk '{print $1}')
+    fi
+    if [ "$ACTUAL" != "$EXPECTED" ]; then
+        echo "[gh] ERROR: checksum mismatch for ${ASSET}"
+        echo "[gh]   expected ${EXPECTED}"
+        echo "[gh]   actual   ${ACTUAL}"
+        rm -f "/tmp/${ASSET}"
+        exit 1
+    fi
+    echo "[gh] Checksum verified for ${ASSET}"
+
+    # Extract based on archive type
+    if [ "$ARCHIVE_EXT" = "zip" ]; then
+        unzip -q "/tmp/${ASSET}" -d /tmp
+    else
+        tar -xzf "/tmp/${ASSET}" -C /tmp
+    fi
+
+    # Install to ~/.local/bin (works in cloud and local)
+    mkdir -p ~/.local/bin
+    cp "${EXTRACT_DIR}/bin/gh" ~/.local/bin/gh
+    chmod +x ~/.local/bin/gh
+
+    # Clean up
+    rm -rf "${EXTRACT_DIR}" "/tmp/${ASSET}"
+
+    echo "[gh] Installed to ~/.local/bin/gh"
+fi
+
+# Verify gh is now in PATH
+if ! command -v gh &> /dev/null; then
+    echo "[gh] ERROR: gh CLI still not found in PATH after installation"
+    echo "[gh] Ensure ~/.local/bin is in your PATH"
+    exit 1
+fi
+
+# Check authentication status
+if [ -n "${GH_TOKEN:-}" ]; then
+    # GH_TOKEN is set, verify it works
+    if gh auth status &> /dev/null; then
+        echo "[gh] Authenticated successfully"
+    else
+        echo "[gh] WARNING: GH_TOKEN is set but authentication check failed"
+        echo "[gh] Token may be invalid or expired"
+    fi
+else
+    echo "[gh] NOTE: GH_TOKEN not set - some operations may require authentication"
+    echo "[gh] See: docs/general/agent-setup/github-cli-setup.md"
+fi
+
+exit 0

flowmark-0.7.2/.claude/scripts/tbd-session.sh

@@ -0,0 +1,27 @@
+#!/bin/bash
+# Ensure the tbd CLI is available and run `tbd prime`.
+# Installed by: tbd setup --auto. Runs on SessionStart and PreCompact.
+#
+# Local-first, then a VERSION-PINNED zero-install fallback. Pinning is both a
+# supply-chain control (an unpinned runner re-resolves to latest on every run
+# and bypasses any cool-off) and a consistency control (every teammate and agent
+# runs the same tbd version).
+
+# Prefer common local bin locations.
+export PATH="$HOME/.local/bin:$HOME/bin:/usr/local/bin:$PATH"
+
+# Local-first: use tbd if it is already on PATH.
+if command -v tbd &> /dev/null; then
+    tbd prime "$@"
+    exit $?
+fi
+
+# Pinned zero-install fallback. Never use an unpinned runner here.
+if command -v npx &> /dev/null; then
+    npx --yes get-tbd@0.2.1 prime "$@"
+    exit $?
+fi
+
+echo "[tbd] tbd CLI not found and npx is unavailable."
+echo "[tbd] Install it with: npm install -g get-tbd@0.2.1"
+exit 1

flowmark-0.7.2/.claude/skills/flowmark/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: flowmark
+description: Fast, consistent Markdown auto-formatter for typographic cleanup (smart quotes, ellipses), normalized formatting, and optional clean line wrapping for small, readable git diffs. Use when creating, editing, or normalizing Markdown (.md) files, cleaning up LLM-generated Markdown, or when the user mentions flowmark or formatting Markdown.
+allowed-tools: Bash(flowmark:*), Bash(uvx:*), Read, Write
+---
+<!-- DO NOT EDIT: `flowmark --install-skill` (format=f02 surface=skill-md) -->
+
+# Flowmark - Markdown Auto-Formatter
+
+Fast, consistent Markdown auto-formatter.
+Run it on Markdown you generate or edit so committed diffs stay small and readable.
+It is conservative and safe to run on every file: it never modifies code blocks or
+inline code.
+
+## Default Usage
+
+Format in place with all auto-formatting (typography, cleanups, semantic line breaks):
+
+```bash
+flowmark --auto FILE   # one file
+flowmark --auto .      # whole tree (respects .gitignore and .flowmarkignore)
+```
+
+Omit `--auto` to preview to stdout; pipe stdin with `-` (e.g. `cat FILE | flowmark -`).
+
+Flowmark ships as two packages with identical formatting and the same `flowmark`
+command: the fast native Rust port [`flowmark-rs`](https://github.com/jlevy/flowmark-rs)
+(recommended) and the Python reference [`flowmark`](https://github.com/jlevy/flowmark).
+Prefer flowmark-rs; reach for the Python build only when you need its library API or the
+very latest patch release not yet ported to Rust.
+If `flowmark` is not on `PATH`, run it with a version-pinned runner (never `@latest`):
+
+```bash
+# Recommended: fast native Rust port
+uvx --from flowmark-rs==0.3.0 flowmark --auto FILE
+# Python reference (library API or newest patch releases)
+uvx --from flowmark==0.7.2 flowmark --auto FILE
+```
+
+## When to Use It
+
+- Auto-format Markdown you create or edit, before committing.
+- Normalize and clean up LLM-generated Markdown.
+- Typographic cleanup (smart quotes, ellipses) and consistent formatting.
+- Optional semantic (sentence-based) line breaks for cleaner git diffs (`--semantic`).
+
+## Full Documentation
+
+Flowmark documents itself.
+Use the CLI rather than reproducing details here:
+
+- `flowmark --help` — every flag: `--semantic`, `--smartquotes`, `--ellipses`,
+  `--width`, `--check`, list spacing, and file discovery
+  (`--extend-include`/`--extend-exclude`).
+- `flowmark --docs` — the full guide: editor on-save setup (VS Code/Cursor), project
+  wiring (pre-commit/CI, `.flowmarkignore`), config files, the Python library API, and
+  installing this skill for other agents (`flowmark --install-skill`).
+
+<!-- This document follows common-doc-guidelines.md.
+See github.com/jlevy/practical-prose and review guidelines before editing.
+-->