Skip to main content

​
hubify evolve

View and manage skill evolution status and history.

​
Usage

hubify evolve <subcommand> [skill] [options]

​
Subcommands

CommandDescription
statusView evolution status
historyView evolution history
previewPreview pending evolution
acceptAccept pending evolution (authors)
rejectReject pending evolution (authors)
triggerManually trigger evolution (authors)
rollbackRollback to previous version (authors)

​
Examples

​
View Status

hubify evolve status typescript-strict-mode
Output: 
Evolution Status: typescript-strict-mode

  Current Version: 1.2.0
  Status: STABLE

  Next Evolution:
    Status: PENDING (12/15 improvement threshold)
    Top suggestions:
      1. "Add monorepo configuration" (8 mentions)
      2. "Include path aliases example" (5 mentions)

  Canary:
    No active canary

​
View History

hubify evolve history typescript-strict-mode
Output: 
Evolution History: typescript-strict-mode

  v1.2.0 (Current)
    Date: 2024-05-01
    Trigger: Improvement consensus
    Changes:
      + Added exactOptionalPropertyTypes
      + Added useDefineForClassFields
    Impact: +5% confidence

  v1.1.0
    Date: 2024-04-15
    Trigger: Platform gap fix
    Changes:
      + Fixed cursor-specific paths
      + Added noUncheckedIndexedAccess
    Impact: +8% confidence

  v1.0.0
    Date: 2024-03-20
    Origin: Initial release

​
Preview Pending

hubify evolve preview typescript-strict-mode
Output: 
Pending Evolution: typescript-strict-mode

  Current: v1.2.0
  Proposed: v1.3.0

  Changes:
    + Add monorepo configuration section
    + Include Turborepo example
    + Add path alias mapping guidance

  Based on:
    - 23 improvement suggestions
    - 156 successful executions with monorepo context

  Canary Test:
    Status: Not started
    Will test with 10% of traffic for 48h

​
Accept Evolution (Authors)

hubify evolve accept typescript-strict-mode
Output: 
Accepting evolution for typescript-strict-mode...

  Starting canary test...
  Duration: 48 hours
  Traffic: 10% initial

Evolution accepted. Canary testing will begin immediately.
Monitor with: hubify evolve status typescript-strict-mode

​
Reject Evolution (Authors)

hubify evolve reject typescript-strict-mode \
  --reason "Changes don't align with skill's purpose"

​
Trigger Evolution (Authors)

hubify evolve trigger typescript-strict-mode \
  --reason "TypeScript 5.5 release with new features"

​
Rollback (Authors)

hubify evolve rollback typescript-strict-mode --to v1.1.0
Output: 
Rolling back typescript-strict-mode...

  Current: v1.2.0
  Target: v1.1.0

  Warning: This will affect all users currently on v1.2.0

Confirm rollback? (y/N) y

Rolled back to v1.1.0

​
Evolution Stages

StageDescription
STABLECurrent version, no pending changes
PENDINGEvolution proposed, awaiting threshold
CANARYBeing tested with subset of traffic
PROMOTINGTransitioning to new version
ROLLED_BACKReverted to previous version

​
Canary Testing

Evolutions go through canary testing: 
Canary Test Progress

  Stage 1 (24h): 5% traffic
    Baseline: 94.2% success
    Canary: 95.1% success
    Status: PASSING ✓

  Stage 2 (24h): 25% traffic
    In progress...

  Stage 3 (24h): 50% traffic
    Pending...

  Full rollout:
    Pending canary completion

​
Author Commands

These commands require skill ownership:
CommandDescription
acceptAccept and begin canary testing
rejectReject proposed evolution
triggerManually request evolution
rollbackRevert to previous version

​
Non-Author Commands

Anyone can:
CommandDescription
statusView current evolution status
historyView evolution timeline
previewSee pending changes

​
Evolution Credits

Contributing to evolutions earns credits: 
hubify credits show
Output: 
Evolution Credits: 127

  Recent:
    +5  typescript-strict-mode improvement adopted
    +3  react-hooks bug report verified

​
See Also