← ClaudeAtlas

aq-workspaces-and-gitlisted

Workspace and git operations for aq worker sessions — the isolated worktree you were assigned, the branch it lives on, and how to commit / push / open PRs from the CLI. Use when you need to check where you're working, inspect the branch state, commit your changes, push, or open a pull request. Also covers workspace release / doctor / reap.
ElectricJack/agent-queue · ★ 7 · Code & Development · score 74
Install: claude install-skill ElectricJack/agent-queue
# aq workspaces + git ## Where am I working? Every worker task acquires a workspace at start. Two places tell you where you are: ```bash pwd # the working directory the daemon put you in echo "$AQ_WORK_DIR" # the same path, from the session environment aq prime # restates work_dir + branch for the held task ``` The branch is on the task row; the workspace path is not, so read the path from the environment above rather than from the task: ```bash aq --json task show <task_id> | jq -r '.data.branch_name' ``` An operator (not a worker token) can see every workspace and its lock holder: ```bash aq project list-workspaces --project-id <pid> # every workspace + who holds each lock ``` ## Git via plain CLI `git` is on `PATH` in every worker session. Prefer plain `git` over any `aq git`/MCP wrapper — it's the same underlying operation with fewer layers. ```bash git status git log --oneline -10 git diff <base>..HEAD --stat git branch --show-current ``` ## Committing your work Every task closes with commits on its branch. The typical pattern: ```bash git add -A # or targeted paths git commit -m "$(cat <<'EOF' feat(scope): concise subject Longer body explaining the *why*, not the *what*. Co-Authored-By: <your-agent-attribution> EOF )" git push -u origin HEAD # first push on a new branch git push # subsequent ``` Commit rules: - **Never `--no-verif