Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Development

kendex-issues

Steward the vanillagreencom/kendex issue queue (Linear team KEN is the poll surface; GitHub stays the PR/code surface) on a self-paced loop: watch open PRs, poll, triage (dedupe; close non-kendex issues and repost project-local ones to their owning repo; fix genuine defects in kendex's skills/agents/hooks/pi-extensions or the Rust CLI), run each fix through the orch skill, merge, propagate via kendex refresh, then reschedule. A thin wrapper: fix cycles belong to orch, PR mechanics to the github skill, PR monitoring to review-gate's pr-watch, Linear ops to the linear skill — this skill carries only the kendex-specific stewardship knowledge. Use when asked to monitor kendex's issues continuously or to run one fix-and-propagate cycle.

vanillagreencom · AI review on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add vanillagreencom/kendex --skill kendex-issues

About this skill


name: kendex-issues description: "Load to monitor kendex's issue queue continuously or to run one fix-and-propagate cycle." summary: "Stewards the kendex issue queue on a self-paced loop: watches open PRs, polls Linear, triages, fixes defects through orch, merges, propagates with kendex refresh."

Project Instructions

Problems with a kendex-owned skill go through kendex report; check ownership in the file first.

kendex Issue Steward

watch → poll → triage → fix → merge → propagate → reschedule. One cycle per turn.

ConcernOwning skill
Fix cycle (prepare → delegate → review → submit → merge)orch
PR threads, replies, reviews, merges, CI logsgithub
Watching open PRsreview-gate pr-watch.sh
Linear reads and writeslinear

Hand-rolled PR mechanics (raw gh api where a github.sh command exists) are a defect.

Loop (one turn)

  1. PR watch: GH_REPO=vanillagreencom/kendex .agents/skills/review-gate/scripts/pr-watch.sh. Silence + exit 0 = nothing needs you. Attention lines → act through the github skill. After a gate-green, also check isInMergeQueue + autoMergeRequest (GraphQL). Queue ejection is silent: re-arm once; a second ejection is a flaky required suite. Quarantine, never re-arm loops.
  2. Poll Linear: linear.sh sync --reconcile, then linear.sh cache issues list --state "Triage,Backlog,Todo,In Progress" --max. Linear is the complete queue (GitHub→Linear sync is one-way); Triage holds the GitHub-synced arrivals. Cross-check gh issue list --repo vanillagreencom/kendex --state open: an open GH issue whose Linear mirror is Done is residue, so close it naming the PR; one with no mirror means the sync broke, so triage it from GitHub and say so. Nothing on either surface → reschedule.
  3. Triage each issue (below); run the fix cycle for each valid defect. Mutate on the issue's home surface: GH-mirrored issues (Linear body links the GH issue) are closed/commented on GitHub; Linear-native ones through the linear skill. PR body carries Closes KEN-<n> plus Closes #<n> when a mirror exists.
  4. After any merge, propagate.
  5. Reschedule (Cadence). Stop only if the user asked.

Triage

  • Already fixed → compare the marker's source=<repo>@<commit7> to the fix commit before investigating.
  • Duplicate → close, name the canonical issue.
  • Not a kendex asset → ownership is the asset's SKILL.md frontmatter (source: kendex), never its install path. Close with the reason; repost project-local items to the owning repo, cross-link, notify that repo's overseer (tmux window 1 of memsira, drovr, hyprtrade). Never fix a consuming repo's defect.
  • Edge case (<1% of users), contrived layout, race between two local processes, or reviewer hypothetical with no report → cancel with the reason. The bar for a kendex issue is a reported symptom.
  • Over-built proposal → cancel; state the simpler approach in one line if one exists.
  • Genuine kendex defect (skills/, agents/, hooks/, pi-extensions/, crates/, ui/) → fix cycle.
  • Unfindable reference → git log -S '<name>' --all first. A name that never existed is a typo: close with the evidence; never ship a shim.
  • Empty body → ask for the concrete repro; leave open.

Fix cycle: load orch

orch owns every step. kendex-specific parameters:

  • Delegate to: generalist (shell/docs/skills), rust (crates/), iced (iced-rs). Tests required; relevant suite green (bash skills/orch/tests/run-all.sh, per-skill tests/*.sh, cargo test --workspace).
  • Scope is the reported symptom (dev skill § Engineering Rules, plus its two exceptions: mechanical enablers ride, an armed defect is in scope). Expect the fix to be about the size of its first commit.
  • Fix direction: determinism and tooling first, meaning a deletion, a short-circuit, or a script. Added prose last. Skills are instructions, not explanations; tools/guard refuses history and reasons in them.
  • Document size: follow doc-limits policy.
  • Review must converge (orch SKILL.md): a recurring defect class is fixed at its source, never per comment. A round that is only scope, test-coverage, or wording asks ends the review: reply, resolve, push nothing, merge through the gate. Replies are Fixed in <sha>, Declined: <reason>, or Tracked: KEN-<n> (issue created first, since the gate rejects a tracking claim naming no issue). Never --admin.
  • Review the diff yourself before submit, finding the actual root cause, not a plausible one. A stalled delegate: inspect its worktree, nudge once.
  • Findings and coupled defects disposition per orch references/finding-disposition.md. The excluded classes come ahead of the defect fork, one reply form per thread.
  • Disjoint files → parallel; same file → sequence or bundle.
  • A required check that cannot be rerun gets a fresh head (commit --amend --no-edit + push --force-with-lease, never-shared heads only); never a merge past red.

Propagate

Only from a change merged on origin/main. Batch: if open items would force another re-vendor soon, hold and run one train; an immediate train is for a fail-open defect in a consumer gate or an owner ask.

  1. git checkout main && git pull --ff-only; confirm the source consumers read sits at the origin/main tip containing the merge.
  2. Skill/agent/hook changes → kendex refresh (all scopes, never --scope project; Pi packages are global) + kendex verify in each consumer. CLI-only changes → binary rebuild, no skill refresh.
  3. Consumer commits: git check-ignore -q <path> first (ignored = nothing to commit). Stage kendex paths only, never -A; revert no-op .kendex-refreshed and template-default churn. Branch → PR → gh pr merge --auto. Reply t
Read the complete source ↗