All authors
Claude Skills by grimoire-rs
github.com/grimoire-rs52 skills0 installs6 views
- Docs InstrumentDocumentation verification gate for a repository that adopted the docs-quality rule set, covering the checks, configs, fixtures, harnesses and reader signals that make those rules enforceable. Use when someone asks to wire up docs checks or a docs CI gate, add doc_type and doc_tier declarations, retrofit a page declaration, set up markdownlint or Vale for prose, check docs links with lychee or a strict build, test documentation examples or code fences, add a doc-example harness, record termin...Votes: 0GitHub stars: 14
- Docs PlanDocumentation discovery and information architecture for a repository, in three tiers (first steps, everyday, integration), with user needs, a page inventory, a coverage table, a delete list, and seeded doc_type and doc_tier declarations. Use when someone asks what documentation a project needs, wants a docs plan, docs audit, docs roadmap, docs IA, page inventory, coverage table, delete list, or content gap analysis, when scoping a quickstart, getting-started page, first-steps page or tutoria...Votes: 0GitHub stars: 14
- Docs ReviewGrade documentation pages against the docs-quality rule set on demand, in any directory and any markup format (Markdown, MDX, reStructuredText, MyST, AsciiDoc). Use when someone asks to review, check, grade, lint or audit a doc page, a README, a changelog, a docs directory or the docs changed on a branch, asks whether a page meets docs-quality, or wants the docs gate run by hand. Not for deciding which pages to write, which is docs-plan, and not for wiring the checks into CI, which is docs-in...Votes: 0GitHub stars: 14
- Hex ArchitectTiered architecture-decision orchestrator — evaluates trade-offs and produces ADRs or system designs through discover, research, design, and adversarial-review phases. Use for architecture decisions, ADRs, system design, trade-off analysis between approaches, one-way-door decisions, C4-level design, or NFR evaluation (scalability, availability, latency, security, cost, operability). Tier (low|medium|high|xhigh|max, auto by default) scales whether the design is delegated to an architect worker...Votes: 0GitHub stars: 14
- Hex CoreShared reference library for the hex swarm-orchestration bundle - worker role registry, model capability matrix, swarm protocol vocabulary, and the .agents/memory/hex.md memory spec. Not invoked directly; the hex-plan, hex-execute, hex-review, hex-architect, and hex-init skills link into it.Votes: 0GitHub stars: 14
- Hex DiscussUse when the user says "let's just discuss this, don't edit anything yet", wants to think a fuzzy problem out loud, or asks to talk something through before a plan or ADR starts. Pre-plan discussion mode — answers first, then fires an automatic entry recon wave, elaborates the ask in dependency-batched questions, pushes back with a structured grill, and captures what was settled in a discussion artifact.Votes: 0GitHub stars: 14
- Hex ExecuteMulti-agent execution orchestrator — implements an approved hex-plan artifact (or a free-text task) as parallel pipelines of serial steps cut along contracts, merges them onto a feature branch, runs one integration gate concurrent with one review, and hands to /hex-finalize. Use to execute, implement, build, or run an approved plan, resume an interrupted execution, or turn a design into tested, reviewed, committed code.Votes: 0GitHub stars: 14
- Hex FinalizeUse when a review-approved feature branch is ready to land and the user asks to finalize it, tidy the commit series, or get the pull request ready to merge. Explicit invocation only — the merge itself stays the human's.Votes: 0GitHub stars: 14
- Hex InitInitialize or reconfigure a project for the hex swarm - audits project context (CLAUDE.md/AGENTS.md) for the knowledge the orchestrators need (how to verify, spec/plan conventions), provisions what is missing into project context, optionally seeds default templates, and bootstraps the AI-maintained swarm memory at .agents/memory/hex.md (cached pointers, orchestration preferences, perspectives of interest). Re-entrant - run again anytime to re-audit pointers or change the setup.Votes: 0GitHub stars: 14
- Hex LoopUse when a settled goal — a discussion, ADR, plan, spec, PR, issue, or existing goal file — should run to completion unattended, and the user wants its goal file plus one paste-ready autonomous-loop prompt for a coding-agent client.Votes: 0GitHub stars: 14
- Hex PlanTiered multi-agent planning orchestrator — decomposes a feature, issue, or PR into a contract-first TDD plan through discover, research, design, decompose, and adversarial-review phases. Use for multi-step feature planning, task decomposition, swarm planning, multi-perspective research, meta-plan preview, or ADR scaffolding. Tier (low|medium|high|xhigh|max, auto by default) scales research depth, whether an architect designs, and review breadth.Votes: 0GitHub stars: 14
- Hex RetroUse when the user asks to run a retrospective over recorded agent friction, consolidate the retro inbox into ledger findings and proposed skill or project-config edits, or import a handwritten friction log; also run at a goal loop's retro checkpoints.Votes: 0GitHub stars: 14
- Hex ReviewTiered adversarial review orchestrator for a working tree, branch diff, pull request, or plan/markdown artifact before it lands on main — a staged reviewer panel (spec, quality, security, performance, docs), root-cause analysis, and a cross-model adversarial pass (codex, medium and up) scale with diff size via tier (low|medium|high|xhigh|max, auto by default). Use for pre-merge checks, code review, branch or PR review, diff review, plan or ADR review, adversarial review, root-cause analysis, ...Votes: 0GitHub stars: 14
- Nox ReviewRun an adversarial review of a code diff or a plan artifact under a second AI harness, headlessly, from an ephemeral git worktree with the repository's own instruction, hook and credential files removed. Use when a change needs a reviewer that did not write it, when a cross-model second opinion is wanted before something lands, or when a plan or an ADR should be argued against by a different model.Votes: 0GitHub stars: 14
- BugfixUse when a bug is reported, something is broken, an error or crash needs fixing, a wrong output appears, or a regression shows up — guides Grimoire's Reproduce → Root-Cause → failing-test-FIRST → Fix → Verify discipline and will not let the fix begin until a failing regression test is recorded. Use also when the user says "bugfix", "/bugfix", "fix this bug", or "something is broken".Votes: 0GitHub stars: 14
- BuilderUse when writing code, fixing a bug, implementing a feature, or improving code structure. Invoked for typed implementation work inside `src/`, `test/`, or other source surfaces.Votes: 0GitHub stars: 14
- Code CheckUse for code review, quality audits, SOLID/DRY consistency checks, pattern audits across the codebase, or verifying anti-pattern compliance across a scope.Votes: 0GitHub stars: 14
- CommitUse when the user says "commit", "/commit", "save progress", or asks to land working changes on a feature or worktree branch. Grimoire working-phase posture — minimises commit count, can amend rolling Checkpoints, offers a one-time PR prompt. For pre-merge cleanup, use `/finalize`.Votes: 0GitHub stars: 14
- DocsUse when authoring or editing Grimoire documentation — user guide, reference pages, doc pages under `docs/`, or doc narrative structure.Votes: 0GitHub stars: 14
- FinalizeUse when the user says "finalize", "/finalize", "prepare this branch for main", "clean up history", "squash the branch", or landing a branch on `main`. Rewrites Checkpoint working-phase commits into clean Conventional Commits before fast-forward merge. Flags: `--squash-all`, `--dry-run`.Votes: 0GitHub stars: 14
- Hex CoreShared reference library for the hex swarm-orchestration bundle - worker role registry, model capability matrix, swarm protocol vocabulary, and the .agents/memory/hex.md memory spec. Not invoked directly; the hex-plan, hex-execute, hex-review, hex-architect, and hex-init skills link into it.Votes: 0GitHub stars: 14
- Hex DiscussUse when the user says "let's just discuss this, don't edit anything yet", wants to think a fuzzy problem out loud, or asks to talk something through before a plan or ADR starts. Pre-plan discussion mode — answers first, then fires an automatic entry recon wave, elaborates the ask in dependency-batched questions, pushes back with a structured grill, and captures what was settled in a discussion artifact.Votes: 0GitHub stars: 14
- Hex FinalizeUse when a review-approved feature branch is ready to land and the user asks to finalize it, tidy the commit series, or get the pull request ready to merge. Explicit invocation only — the merge itself stays the human's.Votes: 0GitHub stars: 14
- Hex InitInitialize or reconfigure a project for the hex swarm - audits project context (CLAUDE.md/AGENTS.md) for the knowledge the orchestrators need (how to verify, spec/plan conventions), provisions what is missing into project context, optionally seeds default templates, and bootstraps the AI-maintained swarm memory at .agents/memory/hex.md (cached pointers, orchestration preferences, perspectives of interest). Re-entrant - run again anytime to re-audit pointers or change the setup.Votes: 0GitHub stars: 14
- Hex LoopUse when a settled goal — a discussion, ADR, plan, spec, PR, issue, or existing goal file — should run to completion unattended, and the user wants its goal file plus one paste-ready autonomous-loop prompt for a coding-agent client.Votes: 0GitHub stars: 14
- Hex RetroUse when the user asks to run a retrospective over recorded agent friction, consolidate the retro inbox into ledger findings and proposed skill or project-config edits, or import a handwritten friction log; also run at a goal loop's retro checkpoints.Votes: 0GitHub stars: 14
- Meta Maintain ConfigUse when creating or editing skills, rules, agents, or hooks under `.claude/`. Also when AI knowledge has drifted from project patterns, a new Claude Code feature lands, or syncing artifacts to current state. Modes: `create`, `audit`, `refresh`, `review`, `research <topic>`.Votes: 0GitHub stars: 14
- Meta Validate ContextUse when auditing the freshness of `.claude/rules/subsystem-*.md` files against current codebase state, or when a subsystem has undergone significant change.Votes: 0GitHub stars: 14
- NextUse when user asks "what''s next" or "next step". Prints next slash command from current state via a sonnet subagent. Flags: `--clear`, `--list`.Votes: 0GitHub stars: 14
- Qa EngineerUse when designing test suites, writing acceptance tests, validating an implementation against a spec, or planning test coverage before implementation. Trigger: /qa-engineer.Votes: 0GitHub stars: 14
- Security AuditorUse for security audits, threat modelling, vulnerability assessment, or evaluating the attack surface of a new capability before merge. Trigger: /security-auditor.Votes: 0GitHub stars: 14
- Ai Config AuthoringCraft effective AI agent configuration — skills, rules, agents, and instructions — for any AI coding client. Use when writing or reviewing a SKILL.md, rule file, or agent definition; when deciding between a skill, rule, hook, or always-on instruction; when a config file grows past its context budget; or when a skill description fails to trigger.Votes: 0GitHub stars: 14
- Grim AuthoringAuthor, validate, and package grim-publishable artifacts — skill directories, rule files, agent definitions, MCP server descriptors, hook manifests, and bundle TOMLs. Use when creating or editing an artifact for grim build or grim release; when choosing frontmatter or catalog metadata fields; when writing a hook.toml with its events, tiers, matchers, and handlers; when adding a vendor-namespaced metadata key for any client grim supports (claude, opencode, copilot, codex, cursor, kiro, junie, ...Votes: 0GitHub stars: 14
- Grim UsageDrive the grim CLI — the OCI package manager for AI skills, rules, agents, MCP servers, hooks, and bundles. Use when installing, updating, searching, rating, or publishing AI-config artifacts with grim; when composing grim init, config, add, lock, install, update, status, context, fetch, describe, export, search, rate, tui, mcp, hook, build, release, publish, login, logout, or completions commands; when configuring settings, multiple registries, or qualified alias/repo references; or when res...Votes: 0GitHub stars: 14
- DocsWrite a minimal SKILL.md, install it from its path, and see an agent load it.Votes: 0GitHub stars: 14
- Architecture GuideSketch a module layout and pick design patterns for a new feature. Use when asked to plan an architecture, choose between approaches, or document a design decision before implementation. The walkthrough starts from the feature's user-visible behaviour and works inward, mapping each responsibility onto a module with a single reason to change, then weighs candidate patterns against the codebase's existing conventions rather than introducing novelty for its own sake. It covers strategy traits fo...Votes: 0GitHub stars: 14
- Code ReviewerReview a diff for SOLID/DRY violations, missing tests, and risky changes. Use when asked to review a pull request, audit a patch, or check code quality before merge.Votes: 0GitHub stars: 14
- Commit HelperDraft a Conventional Commit message from staged changes. Use when the user asks to commit, save progress, or write a commit message.Votes: 0GitHub stars: 14
- Cut ReleaseA release-cutting playbook — version bump, changelog, tag, publish checklist. Published ALONE under a deep nested repo path (playbooks/ci/release/) so the TUI tree folds the single-child chain into one node.Votes: 0GitHub stars: 14
- Hello WorldA minimal smoke-test skill. Use to verify a grimoire install/transform round-trip end to end with the smallest possible artifact.Votes: 0GitHub stars: 14
- Old ReviewerA retired diff reviewer kept only to exercise grim's deprecation surface end to end. Use code-reviewer instead.Votes: 0GitHub stars: 14
- Support DeskRoute a question to the team that owns an artifact. Use when a published skill misbehaves and you need the maintainer, the issue tracker, or the security contact rather than a code change.Votes: 0GitHub stars: 14
- ChangelogUse when a release is being prepared and the site changelog page needs the new version, after `task release:prepare` regenerated CHANGELOG.md, or when the user asks to update the changelog page, write release notes for the site, or backfill a version on `docs/src/content/docs/changelog.md`. User-facing write-up per release — features by outcome with doc links, not the commit list.Votes: 0GitHub stars: 14
- Upstream RefreshUse when grim's upstream knowledge may be stale — a harness shipped or changed a capability, watchlist rows past six months, vendor changelogs since the last check, a deep re-verify of one harness (claude, codex, copilot…), spec or forge claims, or expired research.Votes: 0GitHub stars: 14
- Local SkillPath-sourced golden skill.Votes: 0GitHub stars: 14
- P9 HookishHook-free skill carrying an ignored hook.toml (v1).Votes: 0GitHub stars: 14
- P9 MemberBundle member skill for the Principle 9 fixture (v1).Votes: 0GitHub stars: 14
- P9 SkillPrinciple 9 differential fixture skill (v1).Votes: 0GitHub stars: 14
- P9 HookishHook-free skill carrying an ignored hook.toml (v2).Votes: 0GitHub stars: 14
- P9 MemberBundle member skill for the Principle 9 fixture (v2).Votes: 0GitHub stars: 14