credo

Plugin credo from marketplace marcel-bich-claude-marketplace in Marcel-Bich/marcel-bich-claude-marketplace. Commands read from the repo's manifest — yesterday.

Skills (28)

• audit

  Read-only quality gate that audits already-built work against its stated requirement and Definition of Done before it is allowed to move to 2_done/. Produces a severity-ranked decision proposal (BLOCKER/MAJOR/MINOR/NIT) with evidence; the judgement never edits, only a recorded post-audit step may fi

• budget

  The single source for all API budget cap and reset rules - how much of the 5-hour and weekly API limits may be spent, when to throttle, pause, wake up, or hibernate, and the commit-identity gate that runs before any commit. Use whenever you are about to start or continue autonomous work, before spaw

• compact-plus

  Secure everything the user approved before a context compaction so a later /compact can never lose or alter it. Writes verbatim intent and handoff state to disk and commits plus pushes the tracked work product in the correct repository, then reports whether it is safe to compact. It does NOT run /co

• cross-cutting-checklist-generator

  Detect when a concern is scattered across many places in a project (config keys, enums, translations, feature flags, API endpoints, doc references) and auto-generate a project-local checklist so that same concern is never partially updated again. Use whenever you add or change something that also ex

• diag

  Read-only root-cause diagnosis for a symptom, bug, failure, or unexpected behavior. Establishes the mechanism at file:line and reads up the facts instead of guessing, before any fix is attempted. Produces a diagnosis report; the fix is always a separate step gated by an explicit GO. Use when somethi

• disable

  Disable the credo items workflow for the current directory. Use when the user wants to stop credo's workflow here - for example "stop using credo here", "disable credo for this repo", "turn credo off here", "no credo in this directory", "credo hier aus", "credo hier deaktivieren", "credo hier abscha

• enable

  Enable credo for the current directory. Use when the user wants credo active here - for example "enable credo here", "use credo here", "turn credo on here", "credo hier an", "credo hier aktivieren", "credo hier einschalten" - or runs the /credo:enable command. It persists a per-directory accepted de

• explain

  Explain something on request, at three depths. Use when the user writes "???" (full: What, Why, Example, Consequences), "??" (medium: the same four parts, each short) or "?" (short: two or three bullets) - alone (the last discussed point) at the end of any message ("the audit gate ??", "is xyz so ba

• issue-triage

  Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends ac

• items

  The credo work-item model, where the FOLDER an item file lives in is the single source of truth for its status, gated by a hard Definition of Done. Use whenever you create, update, or track a work item; whenever you decide whether something is "done" and may move to 2_done/; whenever you move an ite

• migrate

  The credo procedure for migrating an existing repo into the .credo/ structure, without any loss risk. Use when migrating a repo into .credo/, onboarding a legacy project into credo, or turning scattered process docs (requirements logs, handoffs, progress notes, audits, plans, specs) and open work in

• optimize

  The credo optimisation audit - an opt-in, read-only scan of a repo for things that slow parallel and long-term work (conflict hotspots, changelog fragments, test-stage convention, dogma settings, parallelism readiness, plus an opt-in instruction-consistency check of the agent instruction sources), w

• orchestration

  Delegate work to subagents safely and efficiently - follow the measured default batch workflow (plan once, builders.min_per_area to builders.max_per_area writing builders per independent area, default 2-4, in worktrees, fresh audit per item, one release per batch), decide how many subagents to run,

• pr-vetting

  Use when the user wants to thoroughly investigate, vet, review, or security-scan a pull request before deciding how to handle it - especially PRs from external or unknown contributors. Runs a parallel multi-agent investigation (technical, security, value/fit, contributor reputation) and merges the f

• requirements-verbatim

  Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decisi

• role-clear

  Clear this session's credo role, returning to the default of NO role (the agent does everything). Use ONLY when the user actually drops the role, in any language, for example "clear the role", "no role", "forget the role", "you are no longer the plan/task agent", "back to doing everything", or Germa

• role-plan

  Assign this session the credo plan/clarify role - the default owner of clarifying items in 1_clarify/, WITHOUT commits or push (the task/build role owns commits and push). Use ONLY when the user actually assigns this role to you, in any language, for example "you are (now) the plan/clarify agent", "

• role-task

  Assign this session the credo task/build role - the default owner of implementing GO items (items in 2_go/), INCLUDING commits and push where dogma permissions allow. Use ONLY when the user actually assigns this role to you, in any language, for example "you are (now) the task/build agent", "you bui

• rules

  Per-repo credo special rules (project-local grants) that live in the target repo's `.credo/RULES.md` and travel with the repo. Load and honor these at the start of every session and inside every subagent, so a project can widen credo's autonomy for itself - for example "in this debug-only repo, rest

• safety

  Hard safety rules that must travel with the project: filesystem-protection and no-autonomous-installs. Use before any delete, rm, shred, unlink, find -delete, mkfs, dd, or wipefs, before removing local files, and before any install (pip, npm, apt, system or global tools). These are the highest-prior

• sandbox

  Do WRITING pre-work for a clarify item that is blocked by a knowledge gap - a missing measurement, a mockup, or a feasibility proof - WITHOUT touching production code, without git, and without disturbing the task / build agent. Use when a 1_clarify item cannot be answered by a product decision alone

• session-active

  The credo behavior for a session running in ACTIVE mode - intensive live collaboration with the user present at the keyboard. Load this when the session-mode inject line says "Load skill session-active", right after the /credo:session-active command, or whenever you are collaborating live and need t

• session-autonomous

  The credo behavior for a session running in AUTONOMOUS mode - work approved GO items unattended while the user is away, hook-enforced self-scheduled keep-alive, budget caps always on. Load this the MOMENT the user hands off full-autonomy, unattended, or AFK work - EVEN BEFORE the mode is set - so th

• session-move

  Move Claude Code sessions from one profile (CLAUDE_CONFIG_DIR, e.g. ~/.claude) to another (e.g. ~/.claude-other): dry-run plan, copy + verify, the user tests the resume in the target, then a cleanup script with literal paths that the USER runs. Execution class C - use ONLY when the user explicitly i

• session-passive

  The credo behavior for a session running in PASSIVE mode - you carry most of the work alongside and the user is available only for clarifications, with no keep-alive. Load this when the session-mode inject line says "Load skill session-passive", right after the /credo:session-passive command, or whe

• skill-capture

  Turn a recurring in-session workflow into a reusable Claude Code skill. Load this the moment you notice you have run the SAME multi-step sequence (same ordered steps or commands, small variation allowed) about three times in the current session, or when open candidates are waiting in .credo/skill-ca

• verify

  Visual verification as the Definition of Done for any change with a runtime surface (a rendered page, a UI, a live view). Use whenever you are about to call a UI or frontend change done, before moving an item to done, whenever an item is marked ui: true, or when someone asks "does it actually render

• wsl-env

  Reach and act on Windows-side services, processes, launchers, and logs when the agent runs inside WSL. Use whenever a service seems unreachable from WSL (a localhost curl fails), when you need to start/stop or inspect a Windows-side process or .ps1 launcher, read Windows logs, hibernate the machine,

Slash commands (21)

• /credo:disable

  credo - Switch the credo items workflow off for this directory and this session (silence onboarding and the workflow text here; model presets and shorthands stay on, reversible)

• /credo:enable

  credo - Enable credo for this directory (opt in; overrides a previous decline)

• /credo:explain

  credo - Explain something in depth (what/why/example/consequences)

• /credo:migrate

  credo - Migrate an existing repo into the .credo/ structure

• /credo:optimize

  credo - Run the optimisation audit for this repo (opt-in, read-only scan, findings offered one by one)

• /credo:peer-lan

  credo - Start, stop, or check the LAN peer relay (cross-machine peer messaging, no cloud)

• /credo:project

  credo - Pin the target repo for credo's project layer (hub-aware), or show the resolved target

• /credo:psalm

  credo - Interactive guide to available topics and workflows

• /credo:role-clear

  credo - Clear this session's default role (back to no role; the agent does everything)

• /credo:role-plan

  credo - Set this session's default role to plan/clarify (owns clarifying 1_clarify items, no commits/push)

• /credo:role-task

  credo - Set this session's default role to task/build (owns implementing GO items incl. commits/push per dogma)

• /credo:sandbox-promote

  credo - Promote an accepted sandbox artifact from .credo/sandbox-tmp/ to .credo/sandbox/

• /credo:self-compact

  credo - Run the real /compact on this session after compact-plus, typed into its own tmux pane once the session is idle with an empty input field

• /credo:self-reload

  credo - Reload plugins and skills of this session (/reload-plugins, /reload-skills typed into its own tmux pane) and wake it with "."; the cheap first try after a plugin update, cc-up only as fallback

• /credo:self-restart

  credo - Restart this Claude Code session and resume exactly the same session in the same profile (e.g. to apply plugin updates)

• /credo:session-active

  credo - Set the session mode to active (intensive live collaboration, no keep-alive)

• /credo:session-autonomous

  credo - Set the session mode to autonomous (work approved GO items unattended, hook-enforced keep-alive ON)

• /credo:session-init

  credo - Initialize session with main agent workflow instructions

• /credo:session-move

  credo - Move Claude Code sessions from one profile (CLAUDE_CONFIG_DIR) to another; plan, copy + verify, user-tested resume, user-run cleanup script

• /credo:session-passive

  credo - Set the session mode to passive (user available for clarifications only, no keep-alive)

• /credo:setup

  credo - Set up Claude Code with recommended workflows and plugins

Hooks (30)

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-paused-wake-guard.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-ask-buffer-guard.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/scripts/credo-5h-budget-guard.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-agent-spawn-check.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-item-move-guard.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-wait-hint.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-peer-message.sh

• PreToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-remote-mirror.sh ask

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-session-start.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-peer-bridge.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-peer-lan-autostart.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/scripts/credo-unblock-sweep.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-optimize-hook.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-todo-tools-hint.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-session-dir-record.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-peer-split-hint.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-permission-mode-record.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-peer-meta-record.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-session-registry.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-reminder.sh start

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/session-mode-inject.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/role-inject.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-datetime-inject.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-attended-reminder.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-skill-nudge.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-plugin-freshness-inject.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-autonomy-clear.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-peer-message.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-peer-bridge.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/credo-optimize-hook.sh

Similar plugins