agentleFS
Sign inStart free
fieldingfielding/skills/tix/SKILL.md

tix

Skill1 starsChanged 4 months agoMITView on GitHub

Command reference and workflow for the `tix` issue tracker. Stores live in per-repo `.tix/` directories. Use whenever you need the exact tix CLI syntax, or when creating, listing, updating, searching, or modeling dependencies between issues. Pair it with a "use tix in every repo" directive in your agent instructions; this skill is the full reference behind it.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. GitoxideLabs/gitoxide★ 12ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All list commands support --json.

    line 37
  2. Very specific:

    Check tix ready before starting work to find unblocked issues.

    line 42
  3. Very specific:

    Commit .tix/issues.jsonl so the tracker travels with the repo.

    line 48

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

tix -- issue tracker

tix tracks issues per-repo in a .tix/ directory. .tix/issues.jsonl is the source of truth: plain JSONL, git-friendly, one issue per line. Run tix ready before starting work to see what's unblocked.

The tool itself is a standalone binary -- install it from github.com/fielding/tix. This skill is just the command reference and workflow conventions for it.

Command reference

tix init [--prefix name]                     # create .tix/ in current dir
tix add "title" [-p 1-5] [-a who] [-t tag]   # create issue (1 = highest pri)
tix list [--status open] [--assignee x]      # list issues
tix ready [--assignee x]                      # unblocked issues only
tix show <id>                                 # full details + comments
tix status <id> open|in_progress|closed       # change status
tix edit <id> [--title/--body/--priority/--assignee/--add-tag/--rm-tag]
tix comment <id> -m "text" [--author x]       # add comment
tix dep add <id> blocks <target>              # id blocks target
tix search "query"                            # full-text search

All list commands support --json. Use -q to get just the ID back (handy for scripting: id=$(tix add "fix login" -p 2 -q)).

Workflow

  • Check tix ready before starting work to find unblocked issues.
  • Set an issue in_progress when you pick it up, closed when it's done.
  • Model blocking relationships with tix dep add <id> blocks <target> so tix ready reflects real ordering.
  • Log decisions and progress as comments rather than rewriting the body.
  • Categorize with tags (bug, enhancement, etc.).
  • Commit .tix/issues.jsonl so the tracker travels with the repo. (Note: if .tix/ is in your global gitignore, committing the JSONL in a repo that wants it tracked needs git add -f .tix/issues.jsonl. Shared/work repos that shouldn't carry a personal tracker stay ignored.)

Notes

  • Priorities run 1-5, where 1 is highest.
  • dep add <id> blocks <target> reads in that direction: <id> must finish before <target> becomes ready.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free