workers

Data Community

Skill notes

Instructions

When the user invokes /workers, show the status of all worktrees and workers:

2. Show Worker Details

For each worktree (excluding main): Branch name and last commit Files changed vs main Whether it's ahead/behind main

3. Format Output

Display as a table:

4. Suggest Actions

Based on status, suggest: Workers with commits → "Ready for PR?" Stale worktrees (no recent commits) → "Clean up?" Workers behind main → "Rebase needed"

5. Quick Actions

Offer shortcuts: /worker-cleanup <worktree> - Remove a specific worktree /worker-pr <branch> - Create PR from worker branch /worker-continue <worktree> "additional task" - Send more work

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Data
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@majiayu000 · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview workers.preview
# 3. Format Output

| Worktree | Branch | Last Commit | Changes | Status |
|----------|--------|-------------|---------|--------|
| ../artemis-issue-42 | feat/issue-42-retry | abc123 Add retry | 3 files | +2 ahead |
| ../artemis-feat-logging | feat/add-logging | def456 Add logs | 5 files | +1 ahead |

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.