@craftsamo/github-tools 0.3.1 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "github-tools",
3
- "version": "0.3.1",
3
+ "version": "0.4.0",
4
4
  "description": "GitHub tools for coding agents: issues, project boards, pull requests, repositories, releases and Actions.",
5
5
  "author": {
6
6
  "name": "craftsamo",
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "github-tools",
3
- "version": "0.3.1",
3
+ "version": "0.4.0",
4
4
  "description": "GitHub tools for coding agents: issues, project boards, pull requests, repositories, releases and Actions.",
5
5
  "author": {
6
6
  "name": "craftsamo",
package/README.md CHANGED
@@ -141,7 +141,8 @@ Add the server to the host's MCP configuration. Flags go in `args`:
141
141
  ## Tools and skills
142
142
 
143
143
  Each toolset comes with a skill that tells an agent how to use its tools. A
144
- toolset with no tools yet registers none (so far only `issues` has tools).
144
+ toolset with no tools yet registers none (so far `issues` and `projects` have
145
+ tools).
145
146
 
146
147
  ### Issues (`issues`)
147
148
 
@@ -161,6 +162,33 @@ The skill is [`github-issues`](skills/github-issues/SKILL.md), shown as
161
162
  An issue's kind is the organization's Issue Type of that name when it defines
162
163
  one, otherwise a `type:<kind>` label.
163
164
 
165
+ ### Project boards (`projects`)
166
+
167
+ | Tool | What it does | Class |
168
+ | ------------------------------- | --------------------------------------------------------------------------------------- | ---------- |
169
+ | `github_project_read` | `view` a board with its fields and views, `list` boards, or `item_list` a board's items | read |
170
+ | `github_project_create` | create a board, or reuse the one of that title, with the standard fields and views | idempotent |
171
+ | `github_project_field_ensure` | add a field, or the missing options of a single select | idempotent |
172
+ | `github_project_view_ensure` | add a saved view with its fields, columns, grouping and sort | idempotent |
173
+ | `github_project_link` | link a board to a repository of the same owner | idempotent |
174
+ | `github_project_unlink` | unlink a board from a repository | idempotent |
175
+ | `github_project_item_add` | put an issue or pull request on a board, or return its item, with field values | idempotent |
176
+ | `github_project_item_create` | create a draft item with field values | add |
177
+ | `github_project_item_edit` | set or clear field values, and change a draft's title and body | overwrite |
178
+ | `github_project_item_archive` | archive an item | overwrite |
179
+ | `github_project_item_unarchive` | bring an archived item back | overwrite |
180
+ | `github_project_item_convert` | turn a draft into an issue, with its kind, labels and milestone | add |
181
+
182
+ The toolset is off by default: add `projects` to `toolsets`. The skill is
183
+ [`github-projects`](skills/github-projects/SKILL.md), shown as
184
+ `github-tools:github-projects` in Claude Code and `github-tools:projects` in
185
+ Hermes. A board is named by its number, `owner/N`, URL or title (`Roadmap` when
186
+ none is given), and found among the boards linked to the repository, then its
187
+ organization's, then the viewer's. The token needs the `project` scope
188
+ (`gh auth refresh -s project`). No API sets a roadmap view's date fields, so
189
+ after `github_project_create` set the Roadmap view's "Date fields" to Start and
190
+ Target in the web UI.
191
+
164
192
  ## Reads and writes
165
193
 
166
194
  Every read tool is named `github_<domain>_read`. Reads can run unasked; writes