LLM Mart Basic
@llm-mart · Joined Jun 2026
Review a diff with the reviewer fleet, funneled to one triaged verdict. Targets the current working diff, a path, or an inbound GitHub PR.
Exploratory spike on a throwaway branch — answer a named question with disposable code. Never merges; exits to a findings note or $ca-feature.
Autonomous sprint — one interactive spec gate, then plan-to-PR execution with every auto-decision SMARTS-scored and logged. Hard gates remain true stops.
Daily repo hygiene — review the day's repo state, then perform the cleanups under per-action confirmation. Fast-forward only, never destructive without a yes.
Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
The sanctioned task-board mutator — add a queued task, start one (flips to in-progress and stamps the date, minting a dotted ID on pick-up), or mark an in-progress task done. The only blessed write to open-tasks.md.
Opt-in lightweight STRIDE pass for a sensitive feature before implementation. Not a routine gate — invoke it when a change warrants security thought.
Deep, rarely-convened whole-codebase audit — eleven specialist lenses, a resumable on-disk audit log, findings filed as GitHub issues on approval. Expensive; estimates cost and STOPs before running. Never a required gate.
Watch a PR's CI to completion — diagnose on red, notify and offer the merge on green. Never auto-merges.
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Five gated phases — frame, shape, refine, write, review-and-appro
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message, comm
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase t
The banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or imports a crypto library. Rejects broken primitives, disabled TLS verification, and home-rolled crypto; the approved-primitive
Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a known bug). Five gated phases: capture, hypothesize, gather, decide, hand off. Investigation only, no code changes; exits to /fix, /adr, or a no-action close.
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only.
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report
The greenfield decomposition interview. Routed to at startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker and no source code exists, or when the user invokes /decompose. A senior-architect persona drives a six-layer interview, persists every layer to disk
The parallel fan-out primitive. Routed to by any skill or command that splits work across independent units and dispatches an agent per unit — subagent-driven-development, /sprint, parallel /review. It owns the dispatch/collect/funnel discipline: bound concurrency, isolate units,
The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Groups tasks into batches, delegates each batch to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint
Use MCP Inspector to connect to local or remote servers, inspect capabilities, call tools, read resources, test prompts, and diagnose failures before release.
Build an MCP server in TypeScript with focused tools, validated schemas, local and remote transports, Inspector tests, and production security controls.
An MCP server exposes tools, resources, or prompts through a standard protocol so an AI application can discover and use external capabilities.
Treat an AI agent skill as both an instruction package and a software dependency: inspect what it says, what it runs, what it can access, and how it updates.
Add remote HTTP or local stdio MCP servers to Claude Code, choose the right scope, protect credentials, verify the connection, and test with least privilege.
Skills teach Claude a repeatable method, connectors provide governed access to apps and live data, and plugins package related capabilities for installation and sharing.
Use an agent skill to package reusable know-how and workflow instructions. Use an MCP server when an agent needs live, governed access to external data or actions.
Custom commands and skills can both create a slash-invoked workflow in Claude Code. The important choice is how the workflow is discovered, shared, and permissioned.
A useful Claude skill solves one recurring engineering job, is easy to inspect, and saves more time than it creates in setup and review.
Claude skills can live in your Claude account, your local Claude Code setup, or a repository. Install them where the sessions that need them can load them.
Build a portable AI agent skill from one repeatable job: a precise description, concise instructions, focused resources, and tests that prove it works.
AI agent skills package instructions, scripts, references, and templates into portable folders an agent loads only when the task calls for them.
AI made publishing cheap, which is exactly the problem. What separates a page worth ranking from a competent summary of the first ten results.
A prompt that works once isn't a quality system. Five cases, an observable rubric, and a regression set will tell you whether a change helped.
One character of YAML, four pods that never started, and two safety nets I didn't know were holding. Every restart is an audit. Schedule them before they schedule you.
"Verify your work" isn't an instruction. It's a mood. Here's the version that's an instruction. Verify with a different mechanism than the one that made the claim.
A prompt that works once may still fail in production. A lightweight eval set gives you repeatable cases, a clear rubric, and a way to see whether a prompt change actually improved the workflow.
The best AI tool is not the one with the longest feature list. It is the one that solves a defined job reliably, fits the workflow, handles data appropriately, and remains useful after the novelty wears off.
Use AI to speed research without losing trust. Learn to find primary sources, verify claims, preserve uncertainty, and keep an auditable source trail.
Better prompts aren't magic wording. They're short briefs that hand the model a task, the context it can't infer, the limits, and a quality bar.
/know
Know
What do I know about a topic
/link
Link
Find and add missing connections
/lint
Lint
Audit structure and repair what is mechanical
/merge
Merge
Merge two pages
/metrics
Metrics
Record a dated metrics snapshot
/monthly
Monthly
The monthly structural review
/orphans
Orphans
Find unreachable pages
/outline
Outline
Outline a piece from your concept pages
/privacy
Privacy
Audit what should not be in the vault
/project-status
Project status
Where a project stands
/project
Project
Create a project
/prune
Prune
Find what is safe to remove
/publish
Publish
Check what is safe to publish
/quiz
Quiz
Test yourself on your own pages
/rename
Rename
Rename a page and fix every link
/report
Report
Write a research report
/retype
Retype
Fix a page's type
/review
Review
Periodic review of what the vault learned
/rollback
Rollback
Undo the last run
/schedule
Schedule
Set up scheduled maintenance
Make any song you can imagine
39 views 0 likesLeading AI-powered video generation platform that specializes in creating hyper-realistic talking avatars
37 views 0 likesHermes Agent is an open-source, self-improving autonomous AI agent developed by Nous Research
36 views 0 likesKilo Code is a popular, open-source AI coding agent and "agentic engineering" platform designed to help developers build, refactor, and debug software faster
34 views 0 likesGeneral-purpose agent in one static Go binary. ReAct loop, ACP server for IDEs, OpenAI-compatible REST API with embedded web UI, Telegram gateway, cron schedule…
20 views 0 likesAutonomous agent framework with structured memory, safety hooks, and loop management. Built by the agent that runs on it.
20 views 0 likesTSP自托管、零运维的 A 股「选股 + 监控 + 回测」量化工作台 | 基于 TickFlow 数据源 | LLM能力驱使策略定制+个股分析+复盘 | 自由接入第三方数据源与个性化扩展数据 | 个人开源 ,非TickFlow官方项目
15 views 0 likesCurated, verified Agent Skills powered by ModelStudio.
18 views 0 likesRun Claude Code, Codex, Antigravity, Cursor Agent and OpenCode as one runtime — persistent sessions, multi-agent councils, an OpenAI-compatible endpoint, an MCP…
17 views 0 likespi had nothing (nothing), so I made something (something) — sorry mariozechner-senpai, I went ahead and lovingly soiled your pure pi for you. opinionated fork o…
14 views 0 likesA persistent workspace for development work that self-improves and continues beyond one session.
33 views 0 likesOpen-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access.
20 views 0 likes📚 A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. Python stdlib only. | http…
28 views 0 likesDeterministic, local-first memory and guardrails for AI coding agents with no LLM in the hot path.
31 views 0 likesDeterministic spec-orchestration for local LLMs in the pi coding agent — drives prompts through refine→research→grill→compose→critique, with bundled web/docs/fe…
20 views 0 likesNative Safari browser automation for AI agents. 97 tools via AppleScript — zero overhead, keeps logins, runs silently in background. Drop-in alternative to Chro…
32 views 0 likesAgent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
15 views 0 likesGit for agent memory. Branches, diffs, PRs, and rollback for what your agents know.
34 views 0 likesMulti-Provider AI Gateway - No personal logs by design. Model autodiscovery, Failover groups, High availability, Android companion app, and more - "Because we h…
16 views 0 likesProduction-grade MCP server for MikroTik RouterOS with secure AI-native network automation.
29 views 0 likes