analyze-repo
Analyze an existing repository's structure, conventions, and guardrails.
Build-in-Public — generate posts from your engineering work, anonymize, and schedule via Buffer
$ npx -y skills add alinaqi/maggy --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
/build-in-publicContext preview
What this command does when you run it.
Build-in-Public — generate posts from your engineering work, anonymize, and schedule via Buffer
description: Build-in-Public — generate posts from your engineering work, anonymize, and schedule via Buffer
To enable the build-in-public plugin for the current project:
/build-in-public enable
This activates post generation for significant work events: PR merged, feature shipped, review passed.
By default, ALL company names are anonymized. To explicitly allow a brand:
/build-in-public add brand Protagé /build-in-public add brand edubites
Brands added this way appear by name in posts. Everything else stays anonymized.
To add a URL that gets appended to posts (especially X/Twitter):
/build-in-public add clickouts to https://github.com/alinaqi/maggy /build-in-public add clickouts to https://edubites.ai
Multiple URLs are supported. X posts always include the first clickout.
Your guidelines are stored in the plugin's `customization.md` file. When you change a setting via slash command, it updates this file:
~/.maggy/plugins/build-in-public/customization.md
The plugin reads this file on every post generation — no restart needed.
/build-in-public disable
Pauses post generation for the current project.
Turn Claude Code into a self-reviewing, test-enforced engineering system that remembers context across sessions — then route work across 13 models from a single dashboard.
Repo: alinaqi/maggy
Analyze an existing repository's structure, conventions, and guardrails.
Full dynamic analysis of workspace topology, dependencies, and contracts.
Checks who's working on the project and optionally converts to a multi-person project with team state management.
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
Run a full drift scan and display all unresolved drift events, grouped by dimension and sorted by severity.
Show the blast radius of a ReasonNode or symbol — what depends on it, what breaks if it changes.