From f796a17f104eb074cd2bf1fa23b227859434a0ae Mon Sep 17 00:00:00 2001 From: softmaxe <94467584+softmaxe@users.noreply.github.com> Date: Thu, 29 Oct 2026 19:59:30 +0800 Subject: [PATCH] chore: remove Matt Pocock skills workflow artifacts --- AGENTS.md | 18 ----------- GLOSSARY.md | 31 ------------------- docs/agents/domain.md | 51 -------------------------------- docs/agents/issue-tracker.md | 45 ---------------------------- docs/agents/merge-and-release.md | 30 ------------------- docs/agents/triage-labels.md | 15 ---------- 6 files changed, 190 deletions(-) delete mode 100644 GLOSSARY.md delete mode 100644 docs/agents/domain.md delete mode 100644 docs/agents/issue-tracker.md delete mode 100644 docs/agents/merge-and-release.md delete mode 100644 docs/agents/triage-labels.md diff --git a/AGENTS.md b/AGENTS.md index be604e0..7d309c5 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -7,21 +7,3 @@ For feature changes, updates, and bug investigation or fixes: 2. Prefer reusing or adapting the upstream approach. 3. Write a custom implementation only when upstream cannot meet the requirements, and briefly explain why. - -## Agent skills - -### Issue tracker - -Issues are tracked in GitHub Issues for `softmaxe/ferry`, via the `gh` CLI. See `docs/agents/issue-tracker.md`. - -### Triage labels - -The five default triage labels, each label string matching its role name. See `docs/agents/triage-labels.md`. - -### Merging and releasing - -Merging a pull request, bumping the version, or publishing a release follows `docs/agents/merge-and-release.md`. - -### Domain docs - -Single-context: one `GLOSSARY.md` and `docs/adr/` at the repo root. See `docs/agents/domain.md`. diff --git a/GLOSSARY.md b/GLOSSARY.md deleted file mode 100644 index 3e3b72a..0000000 --- a/GLOSSARY.md +++ /dev/null @@ -1,31 +0,0 @@ -# ferry - -ferry moves one macOS window to another Space and, by default, switches the screen to it. This -glossary fixes the words used in docs and scripts in both English and Chinese. - -## Language - -**Space**: -One macOS desktop in Mission Control, numbered from 1 across all displays in Mission Control order. -Chinese copy also writes "Space". -_Avoid_: desktop, workspace, 桌面, 空间 - -**Focused window**: -The window that has keyboard focus when ferry runs; the one ferry moves unless told otherwise. -Chinese: 焦点窗口. -_Avoid_: active window, current window, 当前窗口 - -**Destination Space**: -The Space number passed to ferry; it must already exist and must not be a native fullscreen Space. -Chinese: 目标 Space. -_Avoid_: target desktop - -**Follow**: -Switching the screen to the Destination Space after the move; the default, turned off by `--no-follow`. -Chinese: 跟随. -_Avoid_: jump, focus switch - -**Ferry command**: -One Raycast Script Command named "Ferry Window to Space N" that runs ferry with Follow for Space N. -Its name stays in English in Chinese copy, matching what Raycast shows. -_Avoid_: shortcut, extension, 快捷指令 diff --git a/docs/agents/domain.md b/docs/agents/domain.md deleted file mode 100644 index 4032de0..0000000 --- a/docs/agents/domain.md +++ /dev/null @@ -1,51 +0,0 @@ -# Domain Docs - -How the engineering skills should consume this repo's domain documentation when exploring the codebase. - -## Before exploring, read these - -- **`GLOSSARY.md`** at the repo root, or -- **`GLOSSARY-MAP.md`** at the repo root if it exists: it points at one `GLOSSARY.md` per context. Read each one relevant to the topic. -- **`docs/adr/`**: read ADRs that touch the area you're about to work in. In multi-context repos, also check `src//docs/adr/` for context-scoped decisions. - -If any of these files don't exist, **proceed silently**. Don't flag their absence; don't suggest creating them upfront. The `/domain-modeling` skill (reached via `/grill-with-docs` and `/improve-codebase-architecture`) creates them lazily when terms or decisions actually get resolved. - -## File structure - -Single-context repo (most repos): - -``` -/ -├── GLOSSARY.md -├── docs/adr/ -│ ├── 0001-event-sourced-orders.md -│ └── 0002-postgres-for-write-model.md -└── src/ -``` - -Multi-context repo (presence of `GLOSSARY-MAP.md` at the root): - -``` -/ -├── GLOSSARY-MAP.md -├── docs/adr/ ← system-wide decisions -└── src/ - ├── ordering/ - │ ├── GLOSSARY.md - │ └── docs/adr/ ← context-specific decisions - └── billing/ - ├── GLOSSARY.md - └── docs/adr/ -``` - -## Use the glossary's vocabulary - -When your output names a domain concept (in an issue title, a refactor proposal, a hypothesis, a test name), use the term as defined in `GLOSSARY.md`. Don't drift to synonyms the glossary explicitly avoids. - -If the concept you need isn't in the glossary yet, that's a signal: either you're inventing language the project doesn't use (reconsider) or there's a real gap (note it for `/domain-modeling`). - -## Flag ADR conflicts - -If your output contradicts an existing ADR, surface it explicitly rather than silently overriding: - -> _Contradicts ADR-0007 (event-sourced orders), but worth reopening because…_ diff --git a/docs/agents/issue-tracker.md b/docs/agents/issue-tracker.md deleted file mode 100644 index b258aeb..0000000 --- a/docs/agents/issue-tracker.md +++ /dev/null @@ -1,45 +0,0 @@ -# Issue tracker: GitHub - -Issues and specs for this repo live as GitHub issues. Use the `gh` CLI for all operations. - -## Conventions - -- **Create an issue**: `gh issue create --title "..." --body "..."`. Use a heredoc for multi-line bodies. -- **Read an issue**: `gh issue view --comments`, filtering comments by `jq` and also fetching labels. -- **List issues**: `gh issue list --state open --json number,title,body,labels,comments --jq '[.[] | {number, title, body, labels: [.labels[].name], comments: [.comments[].body]}]'` with appropriate `--label` and `--state` filters. -- **Comment on an issue**: `gh issue comment --body "..."` -- **Apply / remove labels**: `gh issue edit --add-label "..."` / `--remove-label "..."` -- **Close**: `gh issue close --comment "..."` - -Infer the repo from `git remote -v`; `gh` does this automatically when run inside a clone. - -## Pull requests as a triage surface - -**PRs as a request surface: no.** _(Set to `yes` if this repo treats external PRs as feature requests; `/triage` reads this flag.)_ - -When set to `yes`, PRs run through the same labels and states as issues, using the `gh pr` equivalents: - -- **Read a PR**: `gh pr view --comments` and `gh pr diff ` for the diff. -- **List external PRs for triage**: `gh pr list --state open --json number,title,body,labels,author,authorAssociation,comments` then keep only `authorAssociation` of `CONTRIBUTOR`, `FIRST_TIME_CONTRIBUTOR`, or `NONE` (drop `OWNER`/`MEMBER`/`COLLABORATOR`). -- **Comment / label / close**: `gh pr comment`, `gh pr edit --add-label`/`--remove-label`, `gh pr close`. - -GitHub shares one number space across issues and PRs, so a bare `#42` may be either: resolve with `gh pr view 42` and fall back to `gh issue view 42`. - -## When a skill says "publish to the issue tracker" - -Create a GitHub issue. - -## When a skill says "fetch the relevant ticket" - -Run `gh issue view --comments`. - -## Wayfinding operations - -Used by `/wayfinder`. The **map** is a single issue with **child** issues as tickets. - -- **Map**: a single issue labelled `wayfinder:map`, holding the Notes / Decisions-so-far / Fog body. `gh issue create --label wayfinder:map`. -- **Child ticket**: an issue linked to the map as a GitHub sub-issue (`gh api` on the sub-issues endpoint). Where sub-issues aren't enabled, add the child to a task list in the map body and put `Part of #` at the top of the child body. Labels: `wayfinder:` (`research`/`prototype`/`grilling`/`task`). Once claimed, the ticket is assigned to the driving dev. -- **Blocking**: GitHub's **native issue dependencies**, the canonical, UI-visible representation. Add an edge with `gh api --method POST repos///issues//dependencies/blocked_by -F issue_id=`, where `` is the blocker's numeric **database id** (`gh api repos///issues/ --jq .id`, _not_ the `#number` or `node_id`). GitHub reports `issue_dependencies_summary.blocked_by` (open blockers only, the live gate). Where dependencies aren't available, fall back to a `Blocked by: #, #` line at the top of the child body. A ticket is unblocked when every blocker is closed. -- **Frontier query**: list the map's open children (`gh issue list --state open`, scoped to the map's sub-issues / task list), drop any with an open blocker (`issue_dependencies_summary.blocked_by > 0`, or an open issue in the `Blocked by` line) or an assignee; first in map order wins. -- **Claim**: `gh issue edit --add-assignee @me`, the session's first write. -- **Resolve**: `gh issue comment --body ""`, then `gh issue close `, then append a context pointer (gist + link) to the map's Decisions-so-far. diff --git a/docs/agents/merge-and-release.md b/docs/agents/merge-and-release.md deleted file mode 100644 index 8db9ad2..0000000 --- a/docs/agents/merge-and-release.md +++ /dev/null @@ -1,30 +0,0 @@ -# Merging and releasing - -The owner tests every change locally before opening a pull request, so pull requests merge without review. Rulesets guard `main` and the release tags instead; this file is the procedure that works within them. - -## Merge a pull request - -1. Run `gh pr merge --squash --auto`. The squash commit takes the pull request's title and body, so the title must be a Conventional Commit. -2. The merge is done when `gh pr view --json state --jq .state` prints `MERGED`. While it waits, check `gh pr view --json mergeStateStatus`: - - `BEHIND`: run `gh pr update-branch `. `main` requires branches to be up to date, and auto-merge does not update them itself. - - `BLOCKED` with a failing `Build and test`: fix the branch and push; auto-merge stays armed. - -## Release a version - -Pushing a `v*.*.*` tag runs `.github/workflows/release.yml`, which builds the binary, publishes the GitHub Release, and updates `Formula/ferry.rb` in `softmaxe/homebrew-tap`. The workflow refuses tags that are not on `main` or that differ from `VERSION` in the `Makefile`. - -1. Choose the next version. When the owner names one, use it. Otherwise count from the latest release tag (`git describe --tags --abbrev=0 origin/main`); when `VERSION` in the `Makefile` is already ahead of that tag, it is the unreleased next version, so release it as is. - - The owner asks to bump the version without naming one: increment the patch number of the tag (v0.0.9 → 0.0.10). When the commits since the tag include a breaking change or a `feat`, tell the owner which bump SemVer would choose. - - Otherwise, apply SemVer to the commits since the tag (`git log --oneline "$(git describe --tags --abbrev=0 origin/main)..origin/main"`): a breaking change bumps major, `feat` bumps minor, anything else bumps patch. -2. Set `VERSION` in the `Makefile` to that version, either in the feature pull request itself or in a pull request titled `chore: release vX.Y.Z`, and merge it as above. -3. Tag the merged commit and push the tag: - - ```bash - git fetch origin main - git tag -a vX.Y.Z -m "Release vX.Y.Z" origin/main - git push origin vX.Y.Z - ``` - -4. Watch the run: `gh run watch "$(gh run list --workflow release.yml --event push --limit 1 --json databaseId --jq '.[0].databaseId')" --exit-status`. The release is done when the run is green, `gh release view vX.Y.Z` lists the `.tar.gz` and `.sha256` assets, and `gh api repos/softmaxe/homebrew-tap/contents/Formula/ferry.rb --jq .content | base64 -d` names `vX.Y.Z`. - -Release tags and published releases are immutable: a ruleset blocks moving or deleting `v*` tags. When a release run fails, re-run it if the failure was transient (`gh run rerun --failed`); otherwise fix forward on `main` and release the next patch version. diff --git a/docs/agents/triage-labels.md b/docs/agents/triage-labels.md deleted file mode 100644 index b716855..0000000 --- a/docs/agents/triage-labels.md +++ /dev/null @@ -1,15 +0,0 @@ -# Triage Labels - -The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker. - -| Label in mattpocock/skills | Label in our tracker | Meaning | -| -------------------------- | -------------------- | ---------------------------------------- | -| `needs-triage` | `needs-triage` | Maintainer needs to evaluate this issue | -| `needs-info` | `needs-info` | Waiting on reporter for more information | -| `ready-for-agent` | `ready-for-agent` | Fully specified, ready for an AFK agent | -| `ready-for-human` | `ready-for-human` | Requires human implementation | -| `wontfix` | `wontfix` | Will not be actioned | - -When a skill mentions a role (e.g. "apply the AFK-ready triage label"), use the corresponding label string from this table. - -Edit the right-hand column to match whatever vocabulary you actually use.