jscraik

Review changed code for behavior-preserving simplification by removing dead code, eliminating duplication, extracting shared helpers, improving names, and tightening tests. Use when a user asks for code review, refactor, clean up PR, simplify, tidy up code, review my changes, or maintainability cleanup before merge.

Check if a repository or agent-facing product surface is ready for AI coding agents. Use when you need to audit repo agent compatibility, review AGENTS.md, find missing test/build commands, evaluate docs quality, assess tool/action parity, or produce a file-evidence scorecard with specific fixes.

Use when reviewing, creating, shrinking, or refactoring AGENTS.md and directly linked instruction guidance that need scoped routing, deduplication, contradiction resolution, or progressive disclosure.

Review code architecture, code quality, dependency graphs, coupling, technical debt, modularization, ownership, and test seams. Use when refactors, restructuring, tightly coupled code, or architecture decisions need proof-backed options.

Choose validation proof for tests, CI, coverage, evals, and closeout evidence: map changed files to repo-native commands, classify pass/fail/blocked ownership, preserve trace/regression artifacts, and keep local, CI, Tessl, external-review, tracker, and runtime truth separate. Use when users ask what tests to run, why validation failed, what proof is enough, or whether command evidence supports a claim.

Defensive review of AI-agent skills, plugins, and tools using Liran Tal's security principles. Use when assessing provenance, permissions, data exposure, sandboxing, or approval boundaries before adoption.

Creates release-ready skill packages from proven workflows by drafting SKILL.md frontmatter, trigger-rich instructions, references/contract.yaml, eval scenarios, task profile, and validation commands. Use when the user asks to create a skill, skillify a workflow, package a process, write SKILL.md, make a reusable skill template, or prepare a skill for release checks.

Run structured AI code review as an advisory closeout gate for local diffs, PR branches, or commits when the user asks for autoreview, Codex review, second-model review, or pre-ship validation.

Validate and align required-check names across GitHub workflows, .harness/ci-required-checks.json, harness.contract.json, and repo docs. Use this skill when CI check names or required-check policy changes.

Validate and diagnose diagram-cli tooling-envelope drift in this repo. Use this skill when work touches docs/agents/tooling.contract.json, scripts/check-environment.sh, scripts/codex-preflight.sh, scripts/verify-work.sh, .codex/environments/environment.toml, or docs that describe local projection behavior.

Diagnose and classify MCP and Local Memory startup failures in this repo. Use this skill when codex mcp list, Codex startup, hook startup, mise trust, or Local Memory listener checks fail.

Validate and align the repo's validation and preflight guidance with the live command contract. Use this skill when AGENTS, README, Makefile, package scripts, validators, or preflight docs change.

Use when a repository needs a small, evidence-bound Coding Harness routine: orient, diagnose, preview installation, verify local work, or distinguish pull-request truth.

Use inside coding-harness when the user wants to find architecture deepening opportunities, reduce shallow/pass-through modules, improve testability, or make the Codex-first harness easier for agents to navigate while staying aligned with docs/roadmap/north-star.md.

Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

Analyze and implement repository-grounded design-system work (tokens, typography, iconography, spacing, styles, aliases, and theme variables) for this monorepo. Use when requests involve UI styling systems or token-layer changes; don’t use for backend/MCP-only tasks with no UI impact. Outputs: evidence-backed analysis or changes with canonical file references, layer impact, and validation commands. Success: work aligns to Brand→Alias→Mapped rules and passes design-system checks.

Guide users through structured co-authoring, improvement, and QA of documentation. Use when users want to write or improve docs such as proposals, technical specs, decision docs, READMEs, guides, API docs, or runbooks; or when they ask for doc review, doc QA, checklists, or templates to make documentation clearer, skimmable, and correct for readers.

Guide users through structured co-authoring, improvement, and QA of documentation. Use when users want to write or improve docs such as proposals, technical specs, decision docs, READMEs, guides, API docs, or runbooks; or when they ask for doc review, doc QA, checklists, or templates to make documentation clearer, skimmable, and correct for readers.