← Back to catalog

▸eds-review

v1.0.0redickowii☍ owners: @redickowii
METADATA
nameeds-review
descriptionEDS Jira review queue and immutable-commit review bridge. Reviews an EDS Jira task from its linked commits (never the working tree), writes a timestamped report into .doc/EDS-XXXX/, and optionally publishes the verdict to Jira. Use when the user says "/eds-review", "eds-review EDS-1234", "отревьюй EDS-1234", "что у меня в Code Review", or asks to review an EDS task by its Jira key.
version1.0.0
licenseMIT
tags
jiracode-reviewgiteds
owners
redickowii
metadata{"author":"redickowii","harnesses":["claude-code","opencode"],"requires":["jira-cli","git","local EDS clones","JIRA_API_TOKEN"],"post_install":"scripts/install.sh"}
SKILL.MD

EDS Review

Bridge between an EDS Jira task, its linked immutable commits, and a documented, evidence-based review verdict.

##When to use

  • /eds-review with no key — show the Code Review queue of the current user.
  • /eds-review EDS-1234 — review that task from its linked commits.
  • Free-form: "отревьюй EDS-1234", "что у меня в Code Review".

##How to run it

Delegate the work to the eds-code-reviewer subagent (Claude Code: Task tool, subagent_type: eds-code-reviewer; opencode: agent eds-code-reviewer). The agent holds the full workflow and safety rules; this skill only maps user intent to that agent's mode.

The agent and the command are registered by scripts/install.sh (the market CLI copies skill files only, it cannot register a subagent). If eds-code-reviewer is not available in the current harness, run that script once — and until then, follow references/agent.body.md inline instead of delegating.

##Prerequisites

jira-cli configured against the self-hosted fssoft Jira, JIRA_API_TOKEN in the environment, and local clones of the EDS repositories under $EDS_WORKSPACE.

##Argument intent (interpret by intent, not a rigid flag grammar)

  • No task key — inspect Jira tasks where status = "Code Review" and Code Reviewer = currentUser(). Report the queue and the most relevant next review; do not write to Jira.
  • EDS-XXXX — review that Jira task from its linked immutable commits.
  • auto, авто, сам, без вопросов or equivalent — work autonomously through discovery, review, validation, documentation, and self-check.
  • Publish intent (status, статус, update Jira, обнови Jira, заверши, or an explicit request for a comment/transition) — in autonomous mode, publish the verified verdict to Jira and make the matching transition.
  • If autonomous Jira-write intent is unclear — do not write to Jira. Ask the user after presenting the verdict.

##Hard rules

  • Apply /review standards to the exact immutable commit range; do not replace the existing /review.
  • Never use git pull, git push, git commit, or working-tree changes as review scope.
  • Reports and task materials live only in the EDS workspace ($EDS_WORKSPACE, default ~/work/EDS) under .doc/EDS-XXXX/, named EDS-XXXX-code-review-YYYY-MM-DD_HH-MM-SS_MSK.md.
  • Verdicts: APPROVED / CHANGES REQUESTED / BLOCKED.

##References

  • references/review-checklist.md — review checklist, severity levels (🔴 critical / 🟡 warning / 🔵 suggestion) and report format.
  • references/agent.body.md — the full eds-code-reviewer workflow (single source for both harnesses).
  • references/command.body.md — the /eds-review command body.
  • references/harness/*.head.md — harness-specific frontmatter used by scripts/install.sh.
  • $EDS_WORKSPACE/AGENTS.md — EDS workspace rules (load first).