Skip to content
cccskills
FreePublished on GitHub

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).

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree
See how to install

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

ci-churn

Free

Measure CI churn cost for a pull request: how many commits and how many CI-compute seconds were burned on avoidable "fix the CI" push rounds. Use when you want to understand the efficiency cost of a PR's iteration cycle, get actionable pre-push check suggestions, or include a churn summary in a pipeline report. Triggers: "ci churn", "how much CI did we burn", "avoidable commits", "ci efficiency", "wasted CI time", "churn report", "/ci-churn". Called automatically by /fp-drift at pipeline close.

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 23, 2026

design-gate

Free

Produce the rendered evidence a human-gated frontend PR owes its reviewer: capture each changed surface (plus the before state for anything modified, plus mobile width), then generate one self-contained local HTML page the founder can open and review without checking anything out. Use when a PR is gated by the "Frontend changes are HUMAN-GATED" section of CLAUDE.md, or when the user says "/design-gate", "screenshot evidence for this PR", "prep this for founder review", "build the design evidence page", "what does this look like before and after". The page comes from a template script, not hand-written markup. Output is session-local and never committed. Do NOT use for non-gated changes: typo/grammar/factual fixes in an unchanged block, dead link targets, alt/ARIA fixes with no visual change, cache-bust bumps, or refactors with no rendered diff.

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 23, 2026

design-iteration

Free

One-fix-at-a-time, approval-gated design fix recovery. Given a checklist of fixes (handover doc, CHECKLIST.md, or inline list), applies each individually, presents a diff, and waits for an explicit APPROVE / REJECT / NO CHANGES decision before committing. Trigger phrases: /design-iteration, "go through the checklist one by one", "fix these one at a time", "bucket recovery", "design fix pass".

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 23, 2026

dev-calibrate

Free

Playbook for correcting a named skill's star level to match its computed Trust Magnitude grade, with an independent post-calibration verification pass and a CLI-logged timeline event (never hand-written). Use when: recalibrating a skill's level, fixing a stale or drifted star rating, running a batch of `gaia dev calibrate` corrections, or confirming a past calibration actually landed. Triggers: "calibrate <skill>", "recalibrate the trust magnitude backlog", "promote/demote <skill> to N stars", "why is <skill> still N stars", "verify a calibration actually landed", "Hall of Heroes ranking is wrong".

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 23, 2026

epic-close

Free

Close out a completed EPIC / sprint end-to-end: author a fact-verified meta-post announcing what shipped, archive the EPIC's handovers, snapshot orchestrator memory, gate the integration→main merge on CI-green + explicit human go, drive the version bump (merge-commit conventions that auto-sync classifies), and verify the release reached the registry/PyPI. Use when the user says "close out EPIC <n>", "wrap up the sprint", "ship the meta shift", "/epic-close", or asks to finalize an integration branch that is ready to merge to main. Generalizes the EPIC 1002 (Yggdrasil II) close-out. This skill orchestrates — it authors founder docs directly (superadmin) and delegates code/regen to workers; it NEVER merges to main without the human gate.

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 23, 2026

ev-adversarial-audit

Free

Run this skill for Phase 3 of the evidence verification pipeline — the adversarial audit step. Use when you need to check the evidence data lake for bad data before ingestion: dead links, wrong URL formats (tree/ vs blob/), subjective wording ("elite", "high-quality"), stale migration notes, benchmark catalog misuse/vendor-claim leakage, or skills whose star evidence conflicts with classified evidence level. Triggers on phrases like: "audit the data lake", "adversarial check", "ev-adversarial-audit", "check for noise in evidence", "flag bad evidence", "run the audit phase", "quality check the by-type files", or any reference to Phase 3 of the pipeline.

The English summary is being prepared. Showing the original description.

gaia-research/gaia-skill-tree23Updated Oct 23, 2026

See all skills by gaia-research

Report a problem with this skill