yolo/agent-skills
3
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: use a generic workspace name in the linearMcp examples

Browse Source
This commit is contained in:
naps62
2026-08-01 13:07:57 +00:00
parent a1f95a1161
commit e449d705c3
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/linear-common/COMMON.md
+2 -2
View File
@@ -64,7 +64,7 @@ GitHub-issues example (`tracker: github`):
| Field | Required | Description | | Field | Required | Description |
|---|---|---| |---|---|---|
| `tracker` | no | Where issues live: `linear` (default), `gitea`, or `github`. See **Tracker backend** below. | | `tracker` | no | Where issues live: `linear` (default), `gitea`, or `github`. See **Tracker backend** below. |
| `linearMcp` | no | MCP server name when `tracker: linear`. Default `linear-server`. Use `linear-acme` for the example workspace. | | `linearMcp` | no | MCP server name when `tracker: linear`. Default `linear-server`. Set a per-workspace name (e.g. `linear-acme`) when a project has its own server. |
| `org` | linear only | Linear organization slug | | `org` | linear only | Linear organization slug |
| `team` | linear only | Linear team name (for listing/creating issues) | | `team` | linear only | Linear team name (for listing/creating issues) |
| `project` | no | Linear project name (narrows issue search). Ignored when `tracker: gitea`. | | `project` | no | Linear project name (narrows issue search). Ignored when `tracker: gitea`. |
@@ -84,7 +84,7 @@ GitHub-issues example (`tracker: github`):
`tracker` selects where issues live. Every instruction below that refers to "the issue" applies to the configured backend; where the two differ (selection, status changes, branch naming) the gitea-specific steps are called out explicitly. `tracker` selects where issues live. Every instruction below that refers to "the issue" applies to the configured backend; where the two differ (selection, status changes, branch naming) the gitea-specific steps are called out explicitly.
- **`linear`** (default): issues live in Linear, accessed via the MCP server named by `linearMcp` (default `linear-server`; an example workspace uses `linear-acme`). Requires `org` + `team`. Tool calls use the `mcp__<linearMcp>__*` prefix. - **`linear`** (default): issues live in Linear, accessed via the MCP server named by `linearMcp` (default `linear-server`; a workspace with its own server sets its own name). Requires `org` + `team`. Tool calls use the `mcp__<linearMcp>__*` prefix.
- **`gitea`**: issues live in the repo's own Gitea issue tracker — **no Linear MCP involved**. The repo (`owner/repo`) is derived from `git remote get-url origin`; the API uses `remoteBaseUrl` + `$GITEA_TOKEN` (load via `source ~/.env.claude` if needed), exactly like the `/work` Gitea PR variant. `org`/`team`/`project` are ignored. - **`gitea`**: issues live in the repo's own Gitea issue tracker — **no Linear MCP involved**. The repo (`owner/repo`) is derived from `git remote get-url origin`; the API uses `remoteBaseUrl` + `$GITEA_TOKEN` (load via `source ~/.env.claude` if needed), exactly like the `/work` Gitea PR variant. `org`/`team`/`project` are ignored.
- **`github`**: issues live in the repo's own GitHub issue tracker — **no Linear MCP involved**. The repo (`owner/repo`) is derived from `git remote get-url origin`; all issue and PR operations use the `gh` CLI (must be authenticated — `gh auth status`). `org`/`team`/`project` are ignored. GitHub has no workflow states, so WIP is signalled by assigning the issue to yourself (like gitea); the PR's `Closes #N` closes the issue on merge. - **`github`**: issues live in the repo's own GitHub issue tracker — **no Linear MCP involved**. The repo (`owner/repo`) is derived from `git remote get-url origin`; all issue and PR operations use the `gh` CLI (must be authenticated — `gh auth status`). `org`/`team`/`project` are ignored. GitHub has no workflow states, so WIP is signalled by assigning the issue to yourself (like gitea); the PR's `Closes #N` closes the issue on merge.