swarm repositories / source
aboutsummaryrefslogtreecommitdiff
path: root/assets/codex-skills
diff options
context:
space:
mode:
authormain <main@swarm.moe>2026-03-20 23:59:48 -0400
committermain <main@swarm.moe>2026-03-20 23:59:48 -0400
commit5474bb6578fa03abaa6b95b9be161e46a743bebb (patch)
tree514adceb8ab191f5a9b79efa8c00160e057e951c /assets/codex-skills
parent5150f5a79658bbf5ca7c33b7b3817ad87b4a5c64 (diff)
downloadjira_at_home-main.zip
Move issues into state dirHEADmain
Diffstat (limited to 'assets/codex-skills')
-rw-r--r--assets/codex-skills/jira-at-home/SKILL.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/assets/codex-skills/jira-at-home/SKILL.md b/assets/codex-skills/jira-at-home/SKILL.md
index 541c7f7..be759d1 100644
--- a/assets/codex-skills/jira-at-home/SKILL.md
+++ b/assets/codex-skills/jira-at-home/SKILL.md
@@ -1,6 +1,6 @@
---
name: jira-at-home
-description: Use when you want brutally basic per-project issue parking in this repository: bind a project, save a freeform note to `issues/<slug>.md`, list existing issue slugs, or read one issue back. Keep the workflow primitive; there are no issue types, statuses, or schema beyond slug plus Markdown body.
+description: Use when you want brutally basic per-project issue parking without touching the worktree: bind a project, save a freeform note to the project’s state-backed `issues/<slug>.md`, list existing issue slugs, or read one issue back. Keep the workflow primitive; there are no issue types, statuses, or schema beyond slug plus Markdown body.
---
-Bind the target project with `project.bind` before issue work unless the MCP was started with `--project`; then use `issue.save` to create or overwrite `issues/<slug>.md`, `issue.list` to enumerate the currently open issue files, and `issue.read` to recover one note body by slug. Treat the store as a tiny parked-ideas notebook, not a tracker: every issue is just freeform Markdown in the canonical `issues/` directory, and the only operational tools worth touching are `system.health` and `system.telemetry` when the transport itself looks suspect.
+Bind the target project with `project.bind` before issue work unless the MCP was started with `--project`; then use `issue.save` to create or overwrite `issues/<slug>.md` under the project’s external state root, `issue.list` to enumerate the currently open issue files, and `issue.read` to recover one note body by slug. Treat the store as a tiny parked-ideas notebook, not a tracker: every issue is just freeform Markdown outside the repo in the canonical `issues/` directory for that project, and the only operational tools worth touching are `system.health` and `system.telemetry` when the transport itself looks suspect.