Skip to content

gaia-research/gaia-skill-tree / .agents/skills/regen

Manually trigger artifact regeneration, versioning, and chore commit. Use when you need fine-grained control over when registry artifacts sync (outside the automated sync-artifacts.yml workflow).

Regen

Manually regenerate registry artifacts, apply version bumps, and commit changes with full control over timing and bump classification.

When to Use

  • Registry changes need immediate artifact sync (not waiting for automated workflow)
  • You want to batch multiple registry/script changes into one controlled sync
  • Testing registry changes locally before pushing
  • Explicit version bump when automated classification might be incorrect
  • Emergency registry fixes that need immediate artifact regeneration

Instructions

Step 1: Verify Registry Changes Exist

Ensure you have uncommitted or staged changes to:

  • registry/nodes/
  • registry/named/
  • registry/schema/
  • registry/suites/
  • scripts/ (if regeneration scripts changed)

Check with: git status

Step 2: Determine Bump Type

Classify the changes as one of:

  • patch: Bug fixes, small registry updates, evidence additions, non-breaking corrections
  • minor: New skills added, new fields added (non-breaking), schema enhancements
  • major: Breaking schema changes, deprecated field removals, BREAKING CHANGE in commit message

Default to patch if uncertain.

Step 3: Run the Sync

Execute the sync with your chosen bump type. Replace BUMP with patch, minor, or major:

cd <project-root>
gaia dev release BUMP
gaia dev docs

Step 4: Verify Generated Changes

Check what was generated:

git status
git diff --stat

Review the version changes in:

  • pyproject.toml
  • packages/cli-npm/package.json
  • registry/gaia.json

Step 5: Commit and Push

If changes look correct:

git config user.name "$(git config user.name)"
git config user.email "$(git config user.email)"
git add .
git commit -m "chore(manual): regenerate registry artifacts and sync docs (bump: BUMP)"
git push

Or if you want to keep the standard message:

git add .
git commit -m "chore(auto): regenerate registry artifacts and sync docs"
git push

Skipping Auto-Sync on Push

If the automated sync-artifacts.yml workflow would conflict with your manual sync, add [skip-gen] to your commit message:

git commit -m "chore(manual): regenerate registry artifacts [skip-gen]"

This prevents the automated workflow from re-running on push.

Notes

  • This skill is for manual, intentional syncs — the default automated workflow (.github/workflows/sync-artifacts.yml) handles routine cases
  • Always review generated artifacts before pushing
  • Version bumps are locked across all packages (pyproject.toml, npm packages, gaia.json)
  • If you make mistakes, use git reset --hard HEAD~1 to undo the last commit
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall