Evref-BL

ARS-derived manuscript review skill for multi-perspective academic critique, methodology review, revision risk analysis, and re-review in DevNexus-Research.

ARS-derived academic paper writing skill for planning, drafting, revising, citation checking, disclosure, and LaTeX-oriented manuscript work in DevNexus-Research.

ARS-derived academic pipeline orchestrator for research-to-paper workflows, integrity gates, review, revision, and handoff in DevNexus-Research.

Use to check whether claims, citations, sources, and bibliography state align.

ARS-derived deep research skill for guided scoping, literature review, evidence synthesis, fact-checking, and systematic review work inside DevNexus-Research projects.

Use to draft, edit, inspect, or diagnose LaTeX manuscripts in an approved scope.

Use to organize source-backed literature review, synthesis notes, and evidence gaps.

Use for read-only manuscript critique, reviewer risk, and revision opportunities.

Record DevNexus progress, verification, blockers, branches, commits, and review gates.

Record DevNexus progress, verification, blockers, branches, commits, and review gates.

Prepare an isolated DevNexus worktree before changing managed files from Claude Code.

Refresh DevNexus-projected Claude Code skills and MCP configuration.

Diagnose DevNexus access before enabling Claude Code integration.

Read DevNexus workspace status, target state, trackers, and blockers.

Prepare an isolated DevNexus worktree before changing managed files.

Refresh DevNexus-projected Codex skills and MCP configuration.

TypeScript quality feedback workflow for using diagnostics, import graphs, Sonar JSON snapshots, touched-file deltas, and rule playbooks before and after source changes. Use when Codex must audit or improve TypeScript quality, triage Sonar findings, or avoid introducing new quality regressions.

TypeScript project topology workflow for separating source, tests, build output, package files, and domain folders without changing behavior. Use when Codex must audit, design, or adjust TypeScript repository layout, especially src/test structure, package publish boundaries, or module grouping.

Dry-run TypeScript bulk rewrite planning workflow for safe repeated mechanical edits, AST matching, preview evidence, rollback strategy, and human approval boundaries. Use when Codex must design or evaluate a TypeScript bulk rewrite/codemod before any broad edit.

TypeScript API boundary review workflow for public exports, package entrypoints, type-only exports, barrels, compatibility, and module ownership. Use when Codex must add, remove, or review exported TypeScript contracts or package-facing APIs.

Systematic TypeScript diagnosis workflow for compiler errors, runtime regressions, failing package scripts, unavailable local binaries, and setup blockers in TypeScript or JavaScript projects. Use when Codex must reproduce, isolate, fix, and verify TypeScript failures without installing dependencies or fetching tools automatically.

Bounded TypeScript refactoring workflow for improving module locality, reducing duplication, splitting broad files, moving types, and preserving public behavior. Use when Codex must change TypeScript structure while keeping verification focused and API compatibility explicit.

TypeScript test hygiene workflow for adding focused coverage, reducing brittle tests, keeping fixtures realistic, and choosing appropriate package scripts. Use when Codex must create, repair, or simplify TypeScript tests without expanding the suite unnecessarily.

Reproduce Pharo smalltalkCI or GitHub Actions failures locally, preferably in Docker; preserve logs; narrow flaky tests; and distinguish project, compatibility, VM/native, and external-service failures.

Reconcile live Pharo, Iceberg, Tonel, and Git state before exporting, reviewing, committing, or pushing image-side changes. Use for dirty or detached Iceberg state, linked worktrees, package-membership mismatches, and image-to-Git delivery.

Recover an unreachable or crashed standalone Pharo MCP image while preserving logs, image files, changes, repository state, and Epicea history. Use for local MCP restart, replacement-image creation, and image-side change recovery.

Load or smoke-test a Pharo project from Tonel, Metacello, or Iceberg and diagnose baseline, branch, source-directory, group, dependency, or version-specific load failures. Use for fresh-image loads and CI-equivalent project loading.

Use PharoCompatibility to load and test a project across supported Pharo versions. Use for missing or renamed Pharo globals, classes, selectors, packages, notices, or semantics; baseline surface selection; and reusable cross-version shims.