jackherd 0.0.1 → 1.0.1

package/CHANGELOG.md

@@ -0,0 +1,65 @@
+# Changelog
+
+What changed for people who use jackherd, newest first.
+
+## 1.0.1
+
+- **README.** Jack's introduction no longer names an author or repeats his name, and the logo has some room above the text.
+
+## 1.0.0
+
+The kit is now called jackherd. The package is `jackherd`, the command `jh`.
+
+- **Rename.** `@crossdelta/agent-kit` becomes `jackherd`, the command `agent-kit` becomes `jh`, the global skill prefix of a new install `jh-` (an existing install keeps its `skillPrefix`). The herdr plugin is `crossdelta.jackherd`.
+- **New places.** Config and lock live in `.jackherd/config.json` and `.jackherd/lock.json`, and everything global under `~/.jackherd/` (config, lock, rules, status line, update check, public-content facts). Skills, agents, hooks and rules that Claude Code reads stay under `.claude/`.
+- **Transition until 2.0.0.** The old names are read and never written; `jh sync` renames the files it finds. The old `agent-kit` command keeps working through a thin `@crossdelta/agent-kit` package that forwards to `jh` and says so once; `agent-kit update` moves an install over. 2.0.0 drops the old names; only `<file>.kit-new` and the recognition of the old `SessionStart` hook command stay.
+- **README.** Starts with the logo and the story of the name, says "coding agents" where it means any of them.
+
+## Before 1.0.0, as @crossdelta/agent-kit
+
+Versions before 0.23.0 are in the repository's history.
+
+## 0.28.0
+
+The watcher reports your own pull requests that no lane works on.
+
+- A documentation or `chore` PR the coordinator opens itself now reports like a lane's: `=== checks failed #<n> (branch <name>)`, `checks passed` and `merged`, and a merge asks every lane to rebase. The watcher finds them with one search for your open pull requests (`gh pr list --author @me`); the first sighting reports nothing.
+- The deploy run after such a merge reports as `(push, #<n>)`.
+- The status block shows them in one line after the coordinator's, `other PRs: #<n> passed · #<m> failed`, at most five, only while there are any.
+
+## 0.27.0
+
+A source can report a change of status, and the dry run checks the mapping.
+
+- `map` takes further named fields (`status`, `priority`, `assignee`, …), and `reportOn` names the fields whose change reports, in place of the content: `=== source tickets T-123 Decide the layout · updated: status In progress → Ready for Dev`. Without `reportOn` a source reports as before. A state saved by 0.26 is read as it is and reports nothing again.
+- `agent-kit watch source … --dry-run` names every `map` field that is empty in all entries, `map.updatedAt: in 23 of 23 entries empty (.fields.updated)`, and then ends with exit code 1; `/follow` does not write such a source.
+- The plan view no longer marks rows only the checkout's board has (`rows from the checkout`, and the footer `rows only in the checkout`). The watcher's coordinator line reminds of them instead: `· board: 2 rows only in the checkout`.
+
+## 0.26.1
+
+Documentation only. The README now says what 0.23.0 to 0.26.0 brought: the badges in the plan view, `/follow`, how a source report reaches you, and a Jira recipe that works with the Atlassian CLI.
+
+## 0.26.0
+
+The plan view shows more on a lane's pull request line.
+
+- A `🌐 preview` badge opens the deploy preview of the pull request's current head.
+- A `💬 <n> new` badge counts the feedback since the last push that `watch.feedback` does not ignore, and `✋ changes requested` shows while a reviewer's latest decisive review asks for changes.
+- The pull request number is a badge too; a folded lane shows each pull request as `↗ #<n> 💬 2`.
+- The numbers come from the watcher's saved state, so the view makes no GitHub call. Without a running watcher, or with a state older than three minutes, there are no badges, and the header says why (`watcher off`, `state 4 min old`).
+
+## 0.25.0
+
+The watcher can report things outside GitHub, and `/follow` sets that up.
+
+- `watch.sources` lists commands that print JSON, for example a ticket search. A new or changed entry arrives at the coordinator as `=== source <name> …`, with its first line and link. The first run of a source is only a baseline; a restart repeats nothing; a failing source reports once and the watcher goes on.
+- `/follow PROJ-123` asks what to follow, checks the tool and its login read only, shows a dry run and writes the source after you agreed. The README has recipes for Jira, Linear, Sentry and GitHub issues.
+- `agent-kit watch source <name> --dry-run` tries a source before the watcher runs it, without touching the watcher's state.
+
+## 0.24.0
+
+The watcher reports how full each lane's context is. A lane that rises to `warn` or `alert` arrives as `=== lane <name> alert 47 %`, and at `alert` the coordinator asks the lane for its hand-over at the end of its current phase instead of waiting for the lane to notice. The status line shows `context warn` or `context alert` beside the lane.
+
+## 0.23.0
+
+The watcher reports deploy previews as an event of their own. When a lane's new head commit has a preview, one line names its link (`watch.previews`), either from GitHub's deployments or from the comment of a bot you list in `authors`. Such a bot's comments no longer count as feedback. Nothing changes without the setting.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 crossdelta
+
+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.

package/NOTICE

@@ -0,0 +1,38 @@
+@crossdelta/agent-kit
+Copyright (c) crossdelta
+
+This package includes material adapted from third-party sources.
+
+--------------------------------------------------------------------------------
+
+mattpocock/skills
+https://github.com/mattpocock/skills, commit 8b78b53
+
+Adapted into the following kit files:
+
+  kit/workflow/skills/grill/SKILL.md                  from skills/productivity/grilling
+  kit/review/skills/diagnose/SKILL.md                 from skills/engineering/diagnosing-bugs
+  kit/workflow/agents/spec-review.md                  from skills/engineering/code-review
+  kit/rules/rules/kit/writing-for-agents.md           from skills/productivity/writing-for-agents
+
+MIT License
+
+Copyright (c) 2026 Matt Pocock
+
+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.