By hylarucoder

Verify a defined software change against requirements and produce a proportional, evidence-backed acceptance report with specification precedence, scope boundaries, requirement-to-evidence…

hylarucoder/hai-stack

Produces a ready-to-run ast-grep command or reusable YAML lint/codemod rule, validated against positive and negative fixtures.

hylarucoder/hai-stack

Reformats and restructures a README or similar Markdown project document without changing its factual content, voice, or scope, then summarizes formatting-only edits.

hylarucoder/hai-stack

Turns supplied content into self-contained HTML and PNG in two modes: card for one shareable frame（知识卡、信息卡、金句卡、封面、把要点做成一张图）, report for multi-section documents（可视化报告、HTML 汇报页、PRD/计划/评审做成网页）.

hylarucoder/hai-stack

Reviews a code change for correctness, security, maintainability, architecture, performance, and verification gaps, or performs a local code-smell review.

hylarucoder/hai-stack

Audits an entity model field by field: what should exist, what exists now, where each value belongs (column, config, computed runtime value, or removal), and what must migrate.

hylarucoder/hai-stack

Challenges an overly conservative, incremental, or compatibility-led proposal with a bold target model, a concrete kill/merge/split list, materially different options, and a falsifiable first proof…

hylarucoder/hai-stack

Pressure-tests an ambitious proposal and returns a landing judgment, one minimum viable proof, explicit cuts, success/failure signals, and a stop rule.

hylarucoder/hai-stack

Investigates architecture and change complexity from repository runtime paths to bounded modules, React components, and shared contracts.

hylarucoder/hai-stack

Audits documentation for internal contradictions and/or mismatches with code, config, schemas, and approved contracts.

hylarucoder/hai-stack

Diagnoses an unexplained software failure through reproduction, competing hypotheses, discriminating checks, and a causal explanation.

hylarucoder/hai-stack

Creates or rewrites a goal document for ambiguous, multi-phase, high-risk, or explicitly planned execution: verifiable outcome, boundary, current state, phases, proof-bearing todos, dry-run, and…

hylarucoder/hai-stack

Evaluates whether an idea, feature, product, or project deserves attention and returns one verdict—Do, Validate first, Reframe, Defer, or Kill—plus the strongest objection and cheapest…

hylarucoder/hai-stack

Recommends names for concepts, identifiers, modules, files, entities, events, or product terms, or audits an existing naming set for misleading vocabulary and viewpoint drift.

hylarucoder/hai-stack

Decides whether a PRD is needed, drafts one from a product problem, repairs an existing PRD, or judges its split/merge boundary.

hylarucoder/hai-stack

Tests whether each requirement, step, role, field, state, module, layer, abstraction, or rule deserves independent existence, then classifies it as Keep, Merge, Defer, Delete, Replace, or Prove first.

hylarucoder/hai-stack

Rebuilds a drifted, repeatedly patched document from verified current conclusions.

hylarucoder/hai-stack

Drives a real behavior change through red-green-refactor and records the failing RED evidence, minimal GREEN implementation, refactor decision, and verification commands.

hylarucoder/hai-stack