hyhmrright
- 25 skills
- 0 followers
- 8 hours ago last updated
- ▌ Sync · hyhmrrightSync plugin snapshot to Git. Use when user wants to sync plugins, push snapshot, or after installing/removing plugins.
- ▌ Market Sages · hyhmrright bundleSummon 13 legendary investors — Warren Buffett, Charlie Munger, Benjamin Graham, Michael Burry, Nassim Taleb, Cathie Wood, and 8 more — to analyze any stock. No API keys. No local setup. Just paste a ticker and go.
- ▌ Add Provider · hyhmrright新增 AI Provider，覆盖 ProviderType / PROVIDER_PROFILES / STATIC_MODELS / PROVIDER_FACTORIES / 前端图标 / 三语 i18n 全部六处
- ▌
- ▌
- ▌ New Master Agent · hyhmrright在 sidecar/agents/masters/ 新增投资大师 Agent，覆盖 shared 元数据表、实现与 registry 注册三处
- ▌ Run Iteration Eval · hyhmrrightRun the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the evals", "score this iteration", "measure the skill change", "smoke-test before the full run", or "re-grade existing outputs".
- ▌ Bump Version · hyhmrrightBump the Logic-Lens version across all six metadata locations at once (package.json, the four plugin manifests, and the README badge), then validate. Use when cutting a release or when `npm run validate` reports a version mismatch.
- ▌ Sync Skill Cache · hyhmrright bundleSync the Logic-Lens working-copy skills/ into the installed plugin cache so content-evals test the EDITED skill, not the last published one. ALWAYS run this after editing any skills/**/SKILL.md or guide/_shared file and BEFORE running content-evals — otherwise the eval silently grades stale content and every token is wasted. Also use to verify the cache is in sync ("is the cache fresh?", "did my edit take effect in evals?", "check skill cache drift").
- ▌ Logic Health · hyhmrright bundleSweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where should I focus testing", "onboarding review", "logic overview before we ship", "give me a health overview of this module". SCOPE RULE: prefer multi-file; also trigger for a single module when the user explicitly uses "health check", "health overview", or "logic health" — a concrete failure uses logic-locate; two versions uses logic-diff; explaining a path uses logic-explain; "fix everything" uses logic-fix-all. Do NOT trigger for: style/architecture-only audits, security-only scans, performance-only audits.
- ▌ New Skill · hyhmrrightScaffold a new brooks-lint analysis skill so it passes `npm run validate` and `npm run evals` on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends paired eval scenarios. Triggers when the maintainer asks to "add a new skill", "scaffold a skill", or "create a brooks-lint mode". Do NOT trigger for: editing an existing skill's content, adding a single eval to an existing skill, or authoring skills for some other plugin.
- ▌ Brooks Health · hyhmrright bundleCombined codebase health dashboard that scores a project across all four quality dimensions — PR quality, architecture, tech debt, and test quality — in a single pass, drawing on twelve classic engineering books. Triggers when: user wants an overall quality assessment, asks "how healthy is this codebase?", "run all the checks", "I need a health score before the release", or wants to onboard a new team with a quality overview. Do NOT trigger for: server health checks, HTTP health endpoints, Kubernetes liveness/readiness probes, database health, or application uptime. Also do not trigger when the user specifically requests only one dimension — use the corresponding focused skill instead (brooks-review / brooks-audit / brooks-debt / brooks-test).
- ▌ Brooks Audit · hyhmrright bundleArchitecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books.
- ▌ Brooks Sweep · hyhmrright bundleFull-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution.
- ▌ Logic Locate · hyhmrright bundleLocate the root cause of a CONFIRMED failure via backward-then-forward semi-formal tracing.
- ▌ Logic Review · hyhmrright bundleFind logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy).
- ▌ Logic Fix All · hyhmrright bundleAutonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free.
- ▌
- ▌ Logic Explain · hyhmrright bundleExplain what a specific piece of code actually does for a given input by producing a step-by-step execution trace (interprocedural, with name resolution and type transitions).
- ▌ Logic Diff · hyhmrright bundleCompare two code versions for semantic equivalence via semi-formal tracing of both versions side-by-side.
- ▌ Logic Lens · hyhmrrightAI-powered Claude Code skill that performs deep code review using formal logic and reasoning frameworks to detect bugs, anti-patterns, and security risks beyond what linters catch.
- ▌ Brooks Debt · hyhmrright bundleTech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books.
- ▌ Brooks Lint · hyhmrrightAI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.
- ▌ Brooks Test · hyhmrright bundleReview test-suite quality using established testing literature; identify brittleness, mock abuse, unclear fixtures, weak assertions, slow feedback, and maintenance risks.
- ▌ Brooks Review · hyhmrright bundlePR code review that surfaces decay risks, design smells, and maintainability issues with concrete Symptom → Source → Consequence → Remedy findings, drawing on twelve classic engineering books.