@craftsamo/github-tools 0.6.0 → 0.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@craftsamo/github-tools",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "GitHub tools for coding agents: issues, project boards, pull requests, repositories, releases and Actions.",
   "author": "craftsamo",
   "license": "MIT",

package/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "github-tools",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "description": "GitHub tools for coding agents: issues, project boards, pull requests, repositories, releases and Actions.",
   "author": {
     "name": "craftsamo",

package/plugin.yaml

@@ -1,5 +1,5 @@
 name: github-tools
-version: 0.6.0
+version: 0.7.0
 description: "GitHub tools for coding agents: issues, project boards, pull requests, repositories, releases and Actions."
 manifest_version: 1
 requires_hermes: ">=0.22"

package/skills/github-projects/SKILL.md

@@ -48,11 +48,13 @@ if GitHub reports missing scopes, the user runs `gh auth refresh -s project`.
 
 - **`view`** returns the board, its fields (with single-select options and
   iterations) and its views. Read it before setting values you are unsure of:
-  field and option names come from there.
+  field and option names come from there. A field with `issue_field: true`
+  mirrors one of the organization's issue fields (see Field values).
 - **`list`** returns an `owner`'s boards, or the boards linked to `repo`;
   closed ones only with `include_closed`.
 - **`item_list`** returns a board's items with their field values by field
-  name and their content (issue, pull request or draft). Filter with `status`
+  name and their content (issue, pull request or draft); a column that
+  mirrors an issue field shows the issue's value. Filter with `status`
   (`"Todo,In Progress"`, or `"-Done"` to leave one out), `content_type`,
   `content_repo`, `search` (part of the title) and `include_archived`.
   `truncated: true` means more matched than `limit` (default 100, at most
@@ -81,9 +83,17 @@ open board of that owner and title, so calling it again is safe.
 - `link_repo` links the board to a repository of the **same owner**; GitHub
   links no other. A personal board cannot be linked to an organization's
   repository.
+- `dates: "issue_fields"` (an organization's board only) makes the dates the
+  organization's issue fields **Start date** and **Target date** instead of
+  the board's own Start and Target: an issue then carries the same dates on
+  every board, they are set with `issue_fields` in `github_issue_edit` (the
+  board tools refuse them), and a pull request or draft has none. It is
+  refused before a board is made when the owner is a user or the organization
+  lacks either field. Use it when the user wants dates shared across boards.
 - **Tell the user to set the Roadmap view's date fields.** No API can set
   them, so the roadmap shows no bars until, in the web UI, the view's
-  "Date fields" are set to Start and Target. `notes` in the result says so;
+  "Date fields" are set to Start and Target (or Start date and Target date).
+  `notes` in the result says so;
   pass it on.
 
 `github_project_field_ensure` and `github_project_view_ensure` add one field or
@@ -92,6 +102,13 @@ view and leave an existing one of that name as it is. Options are written
 and sort can only be set when it is created; to change an existing view, the
 user does it in the web UI.
 
+On an organization's board, `github_project_field_ensure` with
+`issue_field: true` adds a column that mirrors one of the organization's issue
+fields (Priority, Start date, Target date or any other it defines) by name,
+without `type` or `options`: the options and the values are the organization's
+and the issue's. Views can show, group and sort by such a column like any
+other. A field of the board's own with the same name blocks it.
+
 ## Items
 
 An item is an issue, a pull request or a draft on a board.
@@ -135,7 +152,12 @@ them; names, options and iterations match without regard to case.
 
 Title, Assignees, Labels, Milestone, Repository, Linked pull requests and
 GitHub's other own fields belong to the issue, not the board: set them with
-`github_issue_edit`. Every field and value is checked before anything is
+`github_issue_edit`. A column that mirrors one of the organization's issue
+fields (`issue_field: true` in `github_project_read`, such as Priority or
+Target date) holds the issue's own value, the same on every board: set it
+with `issue_fields` and clear it with `clear_issue_fields` in
+`github_issue_edit` (or `issue_fields` in `github_issue_create`); the board
+tools refuse it. Every field and value is checked before anything is
 written, so a refused call wrote nothing.
 
 ### Editing and archiving