菜单
Cross-repo GitHub Project board is the canonical task queue. Use whenever picking work, claiming an issue, transitioning Stage, or filing/closing a backlog issue across image-scoring-backend or image-scoring-gallery.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Bump semver + promote CHANGELOG Unreleased via compiled harness. Use for /release, version bumps, or tagging. Runs scripts/agent_skills/release_bump.py; LLM only when Unreleased is ambiguous. Never commit/push unless the user asks.
Vexlum Scoring MCP — compact search+dispatch on is-be-mcp / is-be-live and gallery is-ui-mcp / is-ui-live.
Choose CLI tools and safe patterns before repo work. Install checklist, bounded search/read commands, and confirmation gates. Use when navigating the codebase, running shell commands, or setting up agent tooling on Windows, WSL2, or macOS.
Inspect JSON, YAML, and API responses with jq, yq, dasel, curl, and httpie. Use for package.json, config.json, and backend health checks. Never output secrets or full credential-bearing config.
Backend build, test, lint, and verify workflows via WSL pytest, ruff, doctor, and docker compose. Use before claiming work complete or opening a PR. Do not invent ad hoc Python commands outside documented venvs.
Choose and run the right search tool: rg vs grep vs ast-grep vs fd vs fzf. Bounded repo navigation with ripgrep, fd, tree, bat, and structural search. Use when finding symbols, files, syntax patterns, or deciding which CLI search to use before reading or editing code.
| name | backlog-queue |
| description | Cross-repo GitHub Project board is the canonical task queue. Use whenever picking work, claiming an issue, transitioning Stage, or filing/closing a backlog issue across image-scoring-backend or image-scoring-gallery. |
The canonical task queue is the GitHub Project board: https://github.com/users/synthet/projects/1
It spans both repos:
synthet/image-scoring-backendandsynthet/image-scoring-gallery. The repoTODO.mdfiles are pointers only — never add tasks there.
Do not hand-roll gh project item-edit or rediscover Stage option IDs.
python scripts/agent_skills/backlog_stage.py claim <N>
python scripts/agent_skills/backlog_stage.py claim <N> --repo gallery
python scripts/agent_skills/backlog_stage.py set-stage <N> --stage in_progress
python scripts/agent_skills/backlog_stage.py set-stage <N> --stage blocked --comment "Blocked: …"
python scripts/agent_skills/backlog_stage.py set-stage <N> --stage review
python scripts/agent_skills/backlog_stage.py set-stage <N> --stage done
Slash command /task-claim <N> uses the same harness.
| Owner | Responsibility |
|---|---|
| Code | Assign, project item lookup, Stage transitions |
| LLM | Pick highest-priority Ready card; Blocked comment prose |
| Human | Promote Backlog→Ready; close dead issues |
Closes #N.Stage = Ready, sort priority:p0..p3 (LLM judgment). Do not invent work if Ready is empty./task-claim (code).set-stage … --stage in_progress.set-stage … --stage blocked --comment "…" (LLM writes comment).Closes #<N>; move to review when opening; done after merge if needed.cross-repo).| Family | Values |
|---|---|
area:* | python, db, gradio, electron, docs |
priority:* | p0, p1, p2, p3 |
type:* | bug, feature, refactor, test, chore, epic |
| (special) | cross-repo |
| (status) | obsolete — stay open on Backlog |
Epics: type:epic + GitHub sub-issues (same repo). Cross-repo: paired issues + cross-repo label.
Obsolete: tier-1 close+wontfix; tier-2 open+status:obsolete on Backlog.
TODO.md.Closes #N.scripts/agent_skills/backlog_stage.pyscripts/housekeeping_backlog.pydocs/project/00-backlog-workflow.md.agent/SKILL_COMPILATION.md