claude

galivelop-workflow

Galivelop workshop's workflow for Claude Code.

2 on GitHubby Galivelopv0.5.2MITupdated 2 days ago
/

Plugin galivelop-workflow from marketplace galivelop-workflow in Zeldris/Galivelop-workflow. Commands read from the repo's manifest — 2 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (26)

  • codebase-design

    Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

  • diagnosing-bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

  • domain-modeling

    Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

  • grill-with-docs

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go. Use when the user wants a plan or design stress-tested and the domain docs kept up to date.

  • grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

  • gw-doctor

    Check that Galivelop-workflow is set up correctly in the current project and explain every failure with its fix. Use when something in the workflow misbehaves or after applying or updating it (run by hand with /gw-doctor).

  • gw-harvest

    Collect, as proposals, what projects using Galivelop-workflow changed or invented (edited workflow skills and scripts, new skills, ideas in their retros) since the last harvest. Use when, from the Galivelop-workflow repo, the user asks to harvest, review or gather improvements from connected project

  • gw-init

    Apply Galivelop-workflow to the current project by following the workflow repo's apply guide (new or existing project). Use when starting the workflow in a repo (run by hand with /gw-init).

  • gw-media-content-now

    Produce one unpublished post piece (texts per channel plus images) in a dated folder, from a proposal id or a free topic. Use when the user picks a proposal from gw-media-content, or asks for a single post, announcement or image about something that just happened.

  • gw-media-content

    Propose up to 10 varied, unpublished posts about a project (app, updates, development, AI-workflow data) for its own social channels. Use when the user asks what to post, for post ideas, a content plan or proposals for X, Reddit, LinkedIn, Discord or another channel the project declares.

  • gw-opt-ai

    Optional retrospective for projects with local or self-hosted AI models (Ollama, LM Studio, llama.cpp, vLLM, an embeddings/RAG pipeline). Measures latency, quality (for example RAG recall) and configuration per machine profile from a per-call log, and proposes changes without applying them. Use afte

  • gw-opt-tokens

    Token-spend retrospective: measures where a session's tokens went and proposes environment changes that cut it without worsening results. Use when the user asks to save tokens, after a long or expensive session, before each PR to the protected branch (after the code review, before the retro), or bef

  • gw-orchestrate-dealer

    Run the main session as an orchestrator that deals work out to clean-context subagents, so it can work for hours without /clear. Use for any task of more than one step (a plan task, a batch of fixes, a whole phase), when bringing material from another repo, and when the session context passes ~150k

  • gw-scout-updates

    Optional scout of updates, improvements and migration candidates for a project's dependencies, runtimes, container images, CI actions, tools and AI models. It inventories the architecture, searches primary sources, filters by the project's constraints and only proposes. Use when the user asks for it

  • gw-selector

    Pick the skill and models for the task that is starting. Use at the start of every task, when a bug or a design request arrives, before reviewing a diff for the protected branch, when a block or phase closes, and whenever the user asks which workflow or model fits.

  • gw-update

    Bring a project's copy of Galivelop-workflow up to the workflow repo's current version, showing the template changes before applying what the user confirms. Use after the workflow publishes a new version (run by hand with /gw-update).

  • improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. Use when the user wants to find architecture or refactoring opportunities.

  • pr

    Use when writing a PR body.

  • prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

  • research

    Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

  • retro

    Conduct a retrospective on a coding session. Use before each push or PR to the protected branch (after /code-review and /gw-opt-tokens), when a phase or milestone closes, or when the user asks for a retro.

  • to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in. Use when the user needs answers from another person to decide.

  • to-spec

    Turn the current conversation into a spec: no interview, just synthesis of what you've already discussed. Use when the user asks to write up a feature already talked through as a spec or PRD.

  • wait-what

    Stop. That last message did not land: re-pitch it. Use when the user says they did not follow your last message.

  • wayfinder

    Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets, and resolve them one at a time until the way to the destination is clear. Use when an idea is too big and foggy for one session.

  • writing-for-agents

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Hooks (7)

  • SessionStart

    bash "${CLAUDE_PLUGIN_ROOT}"/scripts/session-start.sh

  • SessionStart

    python3 "${CLAUDE_PLUGIN_ROOT}"/scripts/recover.py --state

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}"/scripts/review-before-main.sh

  • PreToolUse

    python3 "${CLAUDE_PLUGIN_ROOT}"/scripts/config-guard.py

  • PreToolUse

    python3 "${CLAUDE_PLUGIN_ROOT}"/scripts/agent-signatures.py

  • PreToolUse

    python3 "${CLAUDE_PLUGIN_ROOT}"/scripts/subagent-cap.py

  • Stop

    python3 "${CLAUDE_PLUGIN_ROOT}"/scripts/before-stop.py

View source on GitHub

Maintain galivelop-workflow?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted