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

refactor: rename tracker common
ci / nix (push) Successful in 8s
Details
ci / lint (push) Successful in 11s
Details

Browse Source
This commit is contained in:
Miguel Palhas
2026-08-20 15:40:17 +01:00
parent 2f092f9ee0
commit 04baf8242a
8 changed files with 46 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/work/SKILL.md
+7 -7
View File
@@ -1,18 +1,18 @@
---
name: work
description: "Pick a task from the tracker (Linear or Gitea issues), implement in a worktree, open a PR, and iterate on reviews autonomously"
description: "Pick a task from GitHub, Gitea, or Linear, implement it in a worktree, open a PR, and iterate on reviews autonomously"
user-invocable: true
args:
- name: input
description: "A Linear issue ID (e.g. ERN-347), a Gitea issue number (e.g. #23), an ad-hoc task description, or omit to auto-pick next unblocked task"
description: "A GitHub or Gitea issue number, a Linear issue ID, an ad-hoc task description, or omit to auto-pick the next unblocked task"
required: false
---
# Work - Proper PR Flow
Autonomous workflow: tracking issue -> worktree -> implementation -> PR -> review iteration -> done. The tracker (Linear or Gitea issues) is selected by `tracker` in `linear.json`.
Autonomous workflow: tracking issue -> worktree -> implementation -> PR -> review iteration -> done. GitHub and Gitea are the primary tracker backends; Linear remains supported. Select one with `tracker` in `.claude/tracker.json`.
**First:** Read `linear-common/COMMON.md` (sibling skill, same skills root) for shared setup instructions.
**First:** Read `tracker-common/COMMON.md` (sibling skill, same skills root) for shared setup instructions.
## Workflow
@@ -34,7 +34,7 @@ Autonomous workflow: tracking issue -> worktree -> implementation -> PR -> revie
Follow the implementation guidelines from COMMON.md.
After implementation is complete:
1. Run the `buildCommand` from the config through the gate — `<skills-root>/linear-common/scripts/gate.sh -- <buildCommand>` (see "Local verification budget" in COMMON.md). All checks must pass before opening a PR. Exit 75 = the machine was busy and it never ran: open the PR and let CI be the check, saying so in the PR body. Exit 137 = memory cap, not a failing test.
1. Run the `buildCommand` from the config through the gate — `<skills-root>/tracker-common/scripts/gate.sh -- <buildCommand>` (see "Local verification budget" in COMMON.md). All checks must pass before opening a PR. Exit 75 = the machine was busy and it never ran: open the PR and let CI be the check, saying so in the PR body. Exit 137 = memory cap, not a failing test.
2. If tests fail, fix them. Do not ship broken code.
3. During implementation, check only the module you touched. This is the one full run.
@@ -47,7 +47,7 @@ Advisory, not a hard gate: for a trivial diff (typo, one-liner, config bump) ski
### 4. Open PR
1. Push the branch: `git push -u origin <branch>`
2. Open a PR. The exact commands depend on `remoteHost` from `linear.json`:
2. Open a PR. The exact commands depend on `remoteHost` from `.claude/tracker.json` (or legacy `.claude/linear.json`):
- `github` (default): see **GitHub variant** below.
- `gitea`: see **Gitea variant** below.
3. PR title and body in both cases:
@@ -90,7 +90,7 @@ Then go to step 5 (`/land <N>`).
## Gitea variant (open PR)
Requires `$GITEA_TOKEN` in the environment (`source ~/.env.claude` if needed) and `remoteBaseUrl` from `linear.json`. Set `BASE=$remoteBaseUrl` and `REPO=<owner>/<repo>` (from `git remote get-url origin`).
Requires `$GITEA_TOKEN` in the environment (`source ~/.env.claude` if needed) and `remoteBaseUrl` from `.claude/tracker.json` (or legacy `.claude/linear.json`). Set `BASE=$remoteBaseUrl` and `REPO=<owner>/<repo>` (from `git remote get-url origin`).
```bash
curl -sS -X POST \