tack-agents 0.1.0__tar.gz

tack_agents-0.1.0/.gitignore

@@ -0,0 +1,7 @@
+.DS_Store
+__pycache__/
+*.pyc
+.venv/
+dist/
+.pytest_cache/
+.ruff_cache/

tack_agents-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 John Foland
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

tack_agents-0.1.0/PKG-INFO

@@ -0,0 +1,80 @@
+Metadata-Version: 2.5
+Name: tack-agents
+Version: 0.1.0
+Summary: Keep your agent skills deployed identically to Claude Code and Codex from one manifest, and audit projects so either agent sees the same instructions, skills and hooks.
+Project-URL: Homepage, https://github.com/chocs-cat/tack
+Project-URL: Issues, https://github.com/chocs-cat/tack/issues
+Author-email: John Foland <john@johnfoland.net>
+License-Expression: MIT
+License-File: LICENSE
+Keywords: agents,claude,cli,codex,skills
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Operating System :: MacOS
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Software Development
+Requires-Python: >=3.11
+Requires-Dist: textual>=8.2.8
+Description-Content-Type: text/markdown
+
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/chocs-cat/tack/master/docs/logo-dark.svg">
+  <img alt="tack" src="https://raw.githubusercontent.com/chocs-cat/tack/master/docs/logo-light.svg" height="64">
+</picture>
+
+Keep your coding agents' skills deployed identically to Claude Code and Codex
+from one manifest of sources — your own skill repos and pinned third-party
+ones — and audit your projects so either agent sees the same instructions,
+skills, and hooks.
+
+`tack sync` deploys skills from the manifest's sources, `tack status` shows
+what is where, `tack outdated` and `tack update` track upstream, `tack add`
+and `tack remove` edit the manifest, `tack doctor` audits, and
+`tack scaffold` applies the fixes it suggests. A `path` source with
+`autocommit = true` (and `autopush`) has its skill edits committed, and
+pushed, whenever a command that changes things runs. A bare `tack` opens a
+TUI over all of it: Skills, Sources and Doctor tabs, with every action
+previewed before it runs. [The design](docs/design.md) has the details.
+
+## Install
+
+```sh
+brew install chocs-cat/tap/tack
+# or
+uv tool install tack-agents     # or: pipx install tack-agents
+```
+
+macOS and Linux, Python 3.11 or later, and git.
+
+## Use
+
+```sh
+tack                      # the TUI
+tack add https://github.com/cloudflare/skills.git --skill wrangler
+tack sync --dry-run       # what would change
+tack sync                 # fetch pinned sources, link skills into every harness
+tack status               # sources, pins, and which skills are linked where
+tack outdated --diff      # what upstream changed in the skills you deploy
+tack update cloudflare    # take it: move the pin, then sync
+tack remove cloudflare    # its table, pin, links and checkout
+tack doctor               # audit the harnesses and the projects under projects.roots
+tack doctor --json        # for scripts; exit 1 when there is an error or warning
+tack scaffold hooks ~/Code/app --dry-run   # the diff a doctor fix would make
+```
+
+## Development
+
+```sh
+uv sync
+uv run tack …             # the checkout, not an installed copy
+uv run pytest && uv run ruff check . && uv run ruff format --check . && uv run ty check
+```
+
+[CONTRIBUTING.md](CONTRIBUTING.md) has the commit convention and how releases
+are cut.
+
+## License
+
+MIT; see [LICENSE](LICENSE).

tack_agents-0.1.0/README.md

@@ -0,0 +1,59 @@
+<picture>
+  <source media="(prefers-color-scheme: dark)" srcset="https://raw.githubusercontent.com/chocs-cat/tack/master/docs/logo-dark.svg">
+  <img alt="tack" src="https://raw.githubusercontent.com/chocs-cat/tack/master/docs/logo-light.svg" height="64">
+</picture>
+
+Keep your coding agents' skills deployed identically to Claude Code and Codex
+from one manifest of sources — your own skill repos and pinned third-party
+ones — and audit your projects so either agent sees the same instructions,
+skills, and hooks.
+
+`tack sync` deploys skills from the manifest's sources, `tack status` shows
+what is where, `tack outdated` and `tack update` track upstream, `tack add`
+and `tack remove` edit the manifest, `tack doctor` audits, and
+`tack scaffold` applies the fixes it suggests. A `path` source with
+`autocommit = true` (and `autopush`) has its skill edits committed, and
+pushed, whenever a command that changes things runs. A bare `tack` opens a
+TUI over all of it: Skills, Sources and Doctor tabs, with every action
+previewed before it runs. [The design](docs/design.md) has the details.
+
+## Install
+
+```sh
+brew install chocs-cat/tap/tack
+# or
+uv tool install tack-agents     # or: pipx install tack-agents
+```
+
+macOS and Linux, Python 3.11 or later, and git.
+
+## Use
+
+```sh
+tack                      # the TUI
+tack add https://github.com/cloudflare/skills.git --skill wrangler
+tack sync --dry-run       # what would change
+tack sync                 # fetch pinned sources, link skills into every harness
+tack status               # sources, pins, and which skills are linked where
+tack outdated --diff      # what upstream changed in the skills you deploy
+tack update cloudflare    # take it: move the pin, then sync
+tack remove cloudflare    # its table, pin, links and checkout
+tack doctor               # audit the harnesses and the projects under projects.roots
+tack doctor --json        # for scripts; exit 1 when there is an error or warning
+tack scaffold hooks ~/Code/app --dry-run   # the diff a doctor fix would make
+```
+
+## Development
+
+```sh
+uv sync
+uv run tack …             # the checkout, not an installed copy
+uv run pytest && uv run ruff check . && uv run ruff format --check . && uv run ty check
+```
+
+[CONTRIBUTING.md](CONTRIBUTING.md) has the commit convention and how releases
+are cut.
+
+## License
+
+MIT; see [LICENSE](LICENSE).