Aiwg Regenerate

Community

jmagly

aiwg-regenerate

Select and execute the canonical refresh, existing-project extraction, or legacy AIWG context regeneration branch

Overview

Publisher	jmagly
Repository	`aiwg`
Skill name	`aiwg-regenerate`
Stars	225
Forks	34
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by jmagly on GitHub. Read the source before you install it.

Installation

Install the Aiwg Regenerate AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/jmagly/aiwg/tree/main/agentic/code/addons/aiwg-utils/skills/aiwg-regenerate
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/jmagly/aiwg/tree/main/agentic/code/addons/aiwg-utils/skills/aiwg-regenerate

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/jmagly/aiwg.git /tmp/aiwg
mkdir -p .claude/skills
cp -r /tmp/aiwg/agentic/code/addons/aiwg-utils/skills/aiwg-regenerate .claude/skills/aiwg-regenerate

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Aiwg Regenerate in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Aiwg Regenerate on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Aiwg Regenerate is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Regenerate Context — Branch Selector

The CLI is the deterministic source of truth for context regeneration. An unqualified invocation previews transactional adoption for an established, not-yet-extracted repository; fresh or already-adopted projects route to the canonical refresh. Mutation of an inferred adoption always requires an explicit --apply. Do not make users choose a branch unless they want to override the selection.

Select and load exactly one linked branch before execution:

Canonical workspace graph — default refresh for new and already-migrated projects.
Existing-project extraction — transactional adoption of stable project metadata and provider context into the canonical graph; preview is the default and --apply is required.
Legacy full injection — compatibility branch; embeds normalized AIWG context inside the provider startup file.

Commands

bash
# Intelligent default (recommended user surface)
aiwg run skill aiwg-regenerate

# Canonical default
aiwg regenerate --workspace [--provider <name>] [--dry-run] [--force]

# Existing-project transactional adoption
aiwg regenerate --existing-project [--provider <name>] [--dry-run|--apply]

# Legacy compatibility
aiwg regenerate --full-inject [--provider <name>] [--dry-run]

--legacy aliases --full-inject. The CLI rejects conflicting branches, unknown options, and missing provider values with usage status.

--existing-project rejects --force and all --no-*-md partial-write flags. It refuses possible credentials and ambiguous directive conflicts, previews the exact extracted block and transaction targets, and prints the rollback command after apply.

Explicit branch flags always win. Without one, the executable selector checks the canonical extractor's complete stable-source inventory and managed markers. A first-time established project is previewed; rerun with --apply to adopt it. An already-extracted or genuinely signal-free project uses --workspace.

Supported shared controls are --dry-run, --provider <name>, --force, --no-aiwg-md, --no-agents-md, and --no-workspace-md. The last option is implicit in legacy mode.

Execution Contract

For an established project, preview the selected branch first.
Preserve operator-authored content outside managed regions.
Never copy possible credentials into generated context.
Execute with aiwg run skill aiwg-regenerate -- <flags> when the provider supports executable skills, or run the equivalent aiwg regenerate command.
Report the selected branch, provider, changed targets, backups, warnings, validation result, and rollback path.

Use aiwg refresh instead when frameworks, agents, skills, rules, commands, or provider deployments also need to be updated.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

run.sh1 KB

Frequently asked questions

What does the Aiwg Regenerate AI skill do?

Select and execute the canonical refresh, existing-project extraction, or legacy AIWG context regeneration branch

Why use Aiwg Regenerate on TypingMind?

Because you install it once and use it with any model. Aiwg Regenerate is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Aiwg Regenerate in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/jmagly/aiwg/tree/main/agentic/code/addons/aiwg-utils/skills/aiwg-regenerate. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Aiwg Regenerate?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Aiwg Regenerate?

As many as you like. As long as a model supports skills, you can use Aiwg Regenerate with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Aiwg Regenerate AI skill free?

Yes. It is published on GitHub by jmagly under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Mcp Apps Builder

Shubhamsaboo

CommunityPopular

**MANDATORY for ALL MCP server work** - mcp-use framework best practices and patterns. **READ THIS FIRST** before any MCP server work, including: - Creating new MCP servers - Modifying existing MCP…

Canary

Post-deploy canary monitoring. (gstack)

Land And Deploy

Land and deploy workflow. (gstack)

Clawsweeper

Use for all ClawSweeper work: OpenClaw issue/PR sweep reports, repair jobs, cloud fix PRs, @clawsweeper maintainer mention commands, trusted ClawSweeper-reviewed autofix/automerge, GitHub Actions…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Regenerate Context — Branch Selector

Commands

Execution Contract

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now