SkillAgentSearch skills...

repo-workflows

Archived autoStudio project

Install / Use

npx skills add Zalamancer/autoStudio --skill repo-workflows

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

51/100

Category

Automation

Supported Platforms

Zed

Our assessment of repo-workflows

repo-workflows scores 51/100 on our quality scale, 2778th of 2,889 Automation skills we index.

Its SKILL.md is 4.7 KB long, well organised into 16 sections with 1 code example: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
17/20
Description
4/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • Our last check on 2026-10-20 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-24. Automated pattern scan on 2026-09-24. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

repo-workflows compared with similar skills

All 4 of these similar skills score higher than repo-workflows; compare them before choosing.

SkillScoreStarsUpdatedFormat
repo-workflows (this skill)by Zalamancer510—SKILL.md
Agent-Reachby Panniantong100101.5k1d agoCLAUDE.md
Scraplingby D4Vinci10089.4k1d agoMCP Server
rufloby ruvnet10079.0ktodayMCP Server
algorithmic-artby anthropics100177.9k32d agoSKILL.md

Frequently asked questions

How do I install repo-workflows?
Run npx skills add Zalamancer/autoStudio --skill repo-workflows. The install tabs above show the steps for each supported agent.
Which AI agents does repo-workflows work with?
It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
Is repo-workflows safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is repo-workflows still maintained?
We could not determine when the repository was last updated.

name: repo-workflows description: Git-history-derived workflows, co-change patterns, and iteration rhythms for ProAnimate. Auto-applied when planning multi-file changes. version: 1.0.0 source: local-git-analysis analyzed_commits: 200 user-invocable: false

ProAnimate Repository Workflows

Patterns extracted from the last 200 commits (2026-03-17 to 2026-03-19).

Commit Conventions

Format: type(scope): description

| Type | Usage | Frequency | |------|-------|-----------| | feat | New features | ~20% of commits | | fix | Bug fixes | ~2% | | Add | New files/features (informal) | ~18% | | Fix | Bug fixes (informal) | ~18% | | Move | Reorganizing tabs/panels | ~6% | | Remove | Cleanup | ~5% | | Replace | Swapping implementations | ~4.5% | | Revert/Restore | Undoing changes | ~4% |

Scopes (when conventional): mobile, core, timeline, api, server

Note: About half of commits use conventional format (feat(scope):), the other half use imperative verbs (Add, Fix, Move). Both are acceptable.

File Co-Change Patterns

These files almost always change together. If you touch one, check the others.

Adding a Panel (3-file rule)

  1. src/types/editor.ts — add tab ID to union type
  2. src/constants/tabGroups.ts — register in TAB_GROUPS array
  3. src/components/layout/LeftPanel/LeftPanel.tsx — add lazy import + PanelContent case

Evidence: 100% of panel-addition commits touch all 3 files.

Moving/Reorganizing Tabs

  1. src/constants/tabGroups.ts — move sub-tab between groups
  2. Sometimes src/types/editor.ts — if TabGroupId changes
  3. Sometimes src/components/layout/LeftPanel/LeftPanel.tsx — if GROUP_ICONS needs update

Whiteboard Feature Changes (5-file cluster)

  1. src/components/panels/WhiteboardPanel.tsx (32 changes — most changed file)
  2. src/components/canvas/WhiteboardDrawingOverlay.tsx (21 changes)
  3. src/components/canvas/WhiteboardLayer.tsx (16 changes)
  4. src/stores/useWhiteboardStore.ts (13 changes)
  5. src/services/whiteboardAnimation.ts (13 changes)

Right Panel Properties

  • src/components/layout/RightPanel/RightPanel.tsx co-changes with any panel that has properties
  • Whiteboard properties panels (Drawing, Text, Stroke) change together

Iteration Rhythms

Revert-Heavy Areas

The whiteboard and drawing tools have a high revert rate (~10 reverts in 200 commits). This indicates:

  • UI preferences are subjective — always confirm visual changes with the user before committing
  • Keep reverts cheap — make small, atomic commits for visual/UX changes
  • Common revert patterns: draw style presets, color picker layouts, cursor icons, brush settings

Mobile Sprint Pattern

Mobile features (feat(mobile):) come in rapid sequential commits (30 commits in 1 day). Each commit is atomic:

  1. Infrastructure first (auth, stores, API client)
  2. Renderers and engines next (DynamicRenderer, TypographyRenderer)
  3. Screens last (browse, editor, projects, export)
  4. Polish/fix passes after (fix(mobile):)

Panel Consolidation Pattern

Recurring pattern of merging panels:

  • Merge Style Effects into Mixed Media panel
  • Merge Camera into Cinema Studio
  • Consolidate SVG Art, Components, Motion AI, and Animations into single Assets tab

Lesson: Before adding a new panel, check if it should merge into an existing one.

High-Churn Files (Touch With Care)

| File | Changes | Risk | |------|---------|------| | WhiteboardPanel.tsx | 32 | Highly iterated, revert-prone | | RightPanel.tsx | 32 | Many panels feed into it | | WhiteboardDrawingOverlay.tsx | 21 | Complex interaction logic | | VideoCanvas.tsx | 20 | Core rendering surface | | WhiteboardLayer.tsx | 16 | Rendering pipeline | | tabGroups.ts | 14 | Tab organization (merge conflicts) | | editor.ts (types) | 13 | Type unions grow frequently |

Architecture Hotspots

Left Panel System

  • LeftPanel.tsx renders all panels through PanelContent switch
  • Tab groups defined in tabGroups.ts drive navigation
  • Large groups (>threshold) show card grid; small groups go direct to panel
  • DrillDownHeader provides prev/next navigation within groups

Layout Hierarchy

EditorLayout
├── TopMenuBar
├── LeftPanel (collapsible, 300px)
│   ├── MainGroupHeader / DrillDownHeader
│   └── PanelContent (lazy-loaded)
├── Center (flex-1)
│   ├── VideoCanvas / BRViewport / RigEditor3DViewport
│   └── Timeline / BRTimeline / Rig3DTimeline
└── RightPanel (context-sensitive properties)

Collapse Toggle Pattern

Toggle buttons for collapsible panels must be siblings of the panel in the flex layout, never children. Placing a toggle inside an overflow-hidden collapsible container causes it to be clipped when collapsed.

Related Skills

View on GitHub
GitHub Stars0
CategoryAutomation
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low