Bryan Grimes
Community@bearded-giant · Philadelphia, PA
Principal Eng: @rechargepayments Owner: Bearded Giant LLC
Agent Skills by Bryan Grimes
Showing 10 vetted skills indexed across 1 GitHub repositories.
bearded-giantgrill
Reviews local branch diffs adversarially, auto-fixes high-confidence findings, and loops until clean.
bearded-giantburn
Executes claude:-marked doit todos autonomously in priority order with claim locks and completion notes.
bearded-giantlocal-cerebro
Delegates code-level questions about indexed repositories to a local cerebro CLI without checking them out.
bearded-giantnotion-publish
Publishes .giantmem markdown docs into a Notion page tree via a local MCP server.
bearded-giantworkspace-rules
Enforces output routing, formatting, and frontmatter rules for .giantmem/ workspace artifacts.
bearded-giantfeature-management
Manages feature folder lifecycle, delta-specs, and feature-scoped output routing in .giantmem/features/.
bearded-giantreview-comment
Drafts human-voiced MR/PR review comments from verified findings and posts them via glab or gh.
bearded-giantship-it
Automates the commit, push, MR description, and merge request creation chain for Git branches.
bearded-giantmcp-builder
Build MCP servers in TypeScript or Python with tool schemas, transports, and evaluations.
bearded-giantmdlive
Serves markdown files as live-reloading HTML previews in the browser using mdlive.
Frequently Asked Questions About Bryan Grimes
FAQPage SchemaWhat tasks can I accomplish with Bearded Giant's skills?▼
You can run adversarial pre-ship code reviews with severity scoring and auto-fixes (grill), burn down prioritized todo lists (burn), query indexed repos without checkout (local-cerebro), publish docs to Notion (notion-publish), manage feature folders (feature-management), post review comments to MRs, ship branches end-to-end (ship-it), build MCP servers, and preview markdown live (mdlive).
Who are these skills designed for?▼
These skills target software engineers working in Claude Code sessions who manage feature branches, merge requests on GitLab or GitHub, and local documentation. They suit developers wanting skeptical pre-MR review gates, feature-scoped planning, and MCP server development in TypeScript or Python.
How do the grill and ship-it skills work together in practice?▼
Run grill on your local branch to get a skeptical staff-engineer review of the diff versus base; it auto-fixes high-confidence sev 2-4 findings across up to 5 loops and flags sev-5 items. Once clean, invoke ship-it to commit, push, generate the MR description, and open the merge request.
What are the prerequisites and dependencies for these skills?▼
Skills require a Claude Code session with git access. notion-publish needs the local notion-multi-mcp server (notion-personal account). local-cerebro requires the local cerebro CLI with indexed repos. review-comment needs prior findings from grill or kai review runs. ship-it refuses to run on base branches like main or master.
How does Notion publishing decide which documents to push?▼
Publishing policy lives in config/notion-publish.yaml. Class 'auto' docs (frontmatter publish: true or listed kinds) publish on write via a PostToolUse hook. Class 'on_request' docs (research, design, review, grill-run) publish only when you say 'publish to notion' or invoke /notion-publish. Plans, tasks, facts, and specs never publish.