cobusgreyling

Install Loop Engineering into a project via the unified CLI front door (@cobusgreyling/loop). Prefer this over invoking loop-init / loop-audit separately. Week-one is report-only; never enable auto-merge or unattended fixes unless the human explicitly asks…

Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or Linear board.

Read loop-constraints.md at the start of every run and enforce every rule. This skill runs BEFORE triage or any action skill. Constraints are binding.

An advanced skill for L3 autonomous loops. When the token budget nears exhaustion, the agent analyzes its ROI and autonomously drafts a negotiation request for a budget increase rather than silently failing.

Check token budget and run-log spend before and after a loop run. Enforces early exit when over budget or when there is no actionable work.

Triage open pull requests for CI status, review comments, and merge readiness. Use in PR babysitter loops. Respects project review norms and required checks.

Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.

Scan merged PRs and commits since a given reference, extract titles, labels, types, and signals. Produces structured input for release notes drafting.

Manage what enters and stays in the context window — pruning, compaction, summary fidelity, ordering — so the agent stays coherent on long runs without inflating cost. Use when the user is hitting context limits, running long agentic loops, paying for…

Design where, when, and how a human gates, reviews, or rescues an LLM agent — without turning the agent into a button labelled "approve". Use when the user is building an agent that takes irreversible actions or operates in regulated workflows and mentions…

Design and validate LLM-as-judge scoring — pairwise vs pointwise, bias correction, anchor calibration, and the cases where a judge is the wrong tool. Use when the user is building an eval, scoring open-ended outputs, or comparing model versions and mentions…

Design memory for an LLM agent — what to keep, where to keep it, and when memory hurts more than it helps. Use when the user is adding memory to an agent and mentions short-term memory, long-term memory, episodic, semantic, conversation history, summary…

Pick the right model per call, not per project — route Opus/Sonnet/Haiku, GPT-5/4o/mini, Gemini Pro/Flash by task, and cut cost without losing quality. Use when the user is choosing model tiers, building a router, or debating Opus-only vs mixed-tier…

Decide when to split work across multiple agents vs one agent with tools, and design the handoffs when you do. Use when the user is sketching a multi-agent system or debugging one, and mentions handoff, delegation, supervisor, swarm, crew, sub-agent,…

Defend an LLM agent against prompt injection — direct, indirect, tool-result, and document-borne. Use when the user is building an agent that reads untrusted content (web pages, emails, documents, tool outputs) or exposes user-provided text to a downstream…

Get reliable structured output (JSON, typed objects) out of an LLM without regex repair, retry loops, or silent corruption. Use when the user is parsing model output, fighting malformed JSON, comparing JSON mode vs function calling vs structured outputs, or…

Independently verify a Grok Build goal is truly complete. Checks GOAL.md done conditions, runs tests, and returns PASS or REJECT with evidence. Use before update_goal(completed: true), when asked to "verify goal", "check if done", or as a reviewer sub-agent…

Verify coverage-target goals: coverage threshold met, no hollow tests, suite green. Use before update_goal(completed: true) on coverage goals.

Verify implement-feature goals: acceptance criteria met, tests for new behavior, checklist complete. Use before update_goal(completed: true) on feature goals.

Verify migrate-module goals: tests green, zero legacy imports, GOAL.md checklist complete. Use before update_goal(completed: true) on module migration goals.

Verify refactor-safely goals: full test lock, no public API breakage, behavior preserved. Use before update_goal(completed: true) on refactor goals.

fixture

Pre-flight check before calling update_goal(completed: true). Ensures verifier ran, tests passed, and GOAL.md checklist is complete. Use when implementer believes work is done, or when asked "can I mark goal complete?"

Break a large request into a bounded, goal-ready objective with verifiable done conditions. Use before /goal when the task is vague, too large, or missing acceptance criteria. Produces GOAL.md draft content.

Perform focused architecture and modularity reviews. Identify boundary violations, god objects, tangled dependencies, and propose the smallest reversible improvements. Use the repo-graph MCP when available. Trigger with "architecture review", "check the…

Enforce conventional commits, clean branch strategy, small focused diffs, and PR-ready history. Use before any commit or when preparing work for review. Triggers: "commit this cleanly", "prepare for PR", "fix the git history", "use git-discipline".

Discover available MCP servers, evaluate their fit, install and configure them safely, and then use them effectively within sessions. Use when the user needs new capabilities (browser control, advanced git, observability, etc.) or when existing MCPs are…

For any non-trivial task, start in Plan Mode, produce a clear step-by-step plan with risks and verification method, and wait for explicit approval before any edits. Use when the user says "plan this", "use plan mode", "don't edit yet", or describes a complex…

Perform focused security reviews on code, diffs, hooks, and MCP servers. Look for auth issues, injection, secret leakage, unsafe tool/MCP usage, and hook risks. Use for any change involving external input, credentials, or agent capabilities. Triggers:…

Run parallel independent subagents on the same investigation or design question, collect structured outputs, then synthesize the best elements or score approaches. Use for complex research, architecture decisions, or when multiple valid strategies exist.…

Apply rigorous test-first development. Write failing tests (or characterization tests) that capture desired behavior before implementing. Maintain high test coverage on changed code. Use for new features, refactors, and bug fixes where regression protection…

Example skill that demonstrates good frontmatter. Used in tests.

Perform a thorough Grok Build readiness audit on a project directory. Detects presence and quality of AGENTS.md, .grok/skills, test setup, CI configuration, git hygiene, and ignore files. Produces a 0-100 score plus actionable recommendations. Use when asked…

Calculate and explain a "Grok Readiness Score" (0-100) for a project based on concrete signals: quality of AGENTS.md / project rules, quantity and validity of skills, test/CI presence, git hygiene, ignore configuration, and verification culture. Use when…

Create high-quality, production-ready Grok Build skills (SKILL.md files). Generates correct YAML frontmatter (name, description with specific triggers, when-to-use, argument-hint), clear numbered steps, tool references, and principles. Use when the user says…