Jira Implement Task
commercetools/ui-kit
Fetch Jira ticket, create branch, implement changes, commit, push, open PR.
Define version control for design files, components, and libraries — branching, naming, and release.
Install Version Control Strategy
$ npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills version-control-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-ops/skills/version-control-strategy .claude/skills/version-control-strategy && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "version-control-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/version-control-strategy into .claude/skills/version-control-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-control-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/version-control-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills version-control-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/design-ops/skills/version-control-strategy .agents/skills/version-control-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "version-control-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/version-control-strategy into .agents/skills/version-control-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-control-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills version-control-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/design-ops/skills/version-control-strategy .cursor/skills/version-control-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "version-control-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/version-control-strategy into .cursor/skills/version-control-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-control-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path design-ops/skills/version-control-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills version-control-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/design-ops/skills/version-control-strategy .gemini/skills/version-control-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "version-control-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/version-control-strategy into .gemini/skills/version-control-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-control-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills version-control-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/design-ops/skills/version-control-strategy .github/skills/version-control-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "version-control-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/version-control-strategy into .github/skills/version-control-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-control-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills version-control-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/design-ops/skills/version-control-strategy .opencode/skills/version-control-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "version-control-strategy" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/version-control-strategy into .opencode/skills/version-control-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "version-control-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
version-control-strategy- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~467 tokens
- SKILL.md length
- 192 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Define version control for design files, components, and libraries — branching, naming, and release.
- File history is chaotic
- SKILL.md covers What You Do, What to Version, Versioning Approaches and Branching Strategy, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tasks that involve Git workflow
What it does
Version Control Strategy is an agent skill from Owl-Listener/designer-skills. Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
Its SKILL.md is about 470 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Frontend & Design, covering Git workflow and Design systems. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- File history is chaotic
- Tasks that involve Git workflow
- Tasks that involve Design systems
Example prompts
- “/version-control-strategy”
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Version Control Strategy loads about 467 tokens when it runs. Until then it costs about 62 tokens; SKILL.md has 192 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 192 words, ~467 tokens.
Download SKILL.mdSave it as
.claude/skills/version-control-strategy/SKILL.md (or your agent's skills folder).- name
- version-control-strategy
- description
- Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use `design-system-governance` (design-systems).
Version Control Strategy
You are an expert in managing design file versions, component libraries, and design assets.
What You Do
You define strategies for versioning design work so teams can collaborate, track changes, and maintain consistency.
What to Version
- Design files (Figma, Sketch, etc.)
- Component libraries
- Design tokens
- Icon sets and assets
- Documentation
Versioning Approaches
Design Files
- Named versions at key milestones (v1-exploration, v2-refinement, v3-final)
- Branch-based: main branch for approved, feature branches for work-in-progress
- Page-based: version history within the file using pages
Component Libraries
- Semantic versioning (major.minor.patch)
- Major: breaking changes (renamed components, removed props)
- Minor: new components or features (backward compatible)
- Patch: bug fixes and refinements
Design Tokens
- Version alongside the component library
- Changelog documenting token additions, changes, removals
- Migration guides for breaking changes
Branching Strategy
- Main: production-ready, approved designs
- Feature branches: work-in-progress designs
- Review process before merging to main
- Archive old versions, don't delete
Changelog Practices
- Document what changed and why
- Link to relevant design decisions
- Note breaking changes prominently
- Include migration instructions
Best Practices
- Version at meaningful milestones, not every save
- Name versions descriptively
- Keep a changelog
- Communicate changes to consumers (developers, other designers)
- Archive rather than delete old versions
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in design-ops/skills/version-control-strategy of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Version Control Strategy next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Version Control Strategy this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~467 | Automated safety check: Pass | MIT | |
| Jira Implement Taskcommercetools/ui-kit | 154 | — | ~1.6k | Automated safety check: Notes | MIT | |
| Scraps Reviewgetsentry/sentry | 46k | — | ~1.2k | Automated safety check: Notes | Custom licence | |
| Architecture Mapalmendili/skills | 382 | 1 repos | ~2.3k | Automated safety check: Pass | None | |
| Plate UIudecode/plate | 17k | — | ~2.6k | Automated safety check: Pass | Custom licence | |
| Fast Agent Designevalstate/fast-agent | 3.9k | — | ~220 | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Scraps Review
getsentry/sentry
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…
Architecture Map
almendili/skills
Build or update an interactive isometric map of a repository's architecture — buildings sized by real measurements, neighborhoods by subsystem, animated flows tracing actual call paths, and a drift…
Plate UI
udecode/plate
Build new shadcn-style components for Plate's registry and editor surfaces.
Fast Agent Design
evalstate/fast-agent
A skill your agent uses to generate well-branded interfaces and assets for fast-agent, either for production or throwaway prototypes/mocks/etc.
- Official
Kaizen UI
NVIDIA/Personal-AI-Router
Kaizen UI (KUI) component library and design-pattern advisor for NVIDIA applications.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Categories
Questions about Version Control Strategy
What does Version Control Strategy do?
Define version control for design files, components, and libraries — branching, naming, and release. Version Control Strategy is an agent skill from Owl-Listener/designer-skills. Define version control for design files, components, and libraries — branching, naming, and release.
When should I use Version Control Strategy?
Version Control Strategy fits situations like: file history is chaotic; tasks that involve Git workflow; tasks that involve Design systems.
How do I install Version Control Strategy in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a claude-code`. Or copy the skill folder (design-ops/skills/version-control-strategy in Owl-Listener/designer-skills) into .claude/skills/version-control-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Version Control Strategy in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a codex`. Or copy the skill folder (design-ops/skills/version-control-strategy in Owl-Listener/designer-skills) into .agents/skills/version-control-strategy in your project. Codex loads it when a task matches its description.
Can I use Version Control Strategy in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill version-control-strategy -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/version-control-strategy, .gemini/skills/version-control-strategy, .github/skills/version-control-strategy and .opencode/skills/version-control-strategy in your project.
What does Version Control Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Version Control Strategy is instructions for the agent only.
Does Version Control Strategy access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Version Control Strategy safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Version Control Strategy use?
Version Control Strategy is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Version Control Strategy use?
About 467 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Version Control Strategy?
Skills that share tags, products or a category with Version Control Strategy: Jira Implement Task (commercetools/ui-kit, 154 stars), Scraps Review (getsentry/sentry, 46k stars), Architecture Map (almendili/skills, 382 stars) and Plate UI (udecode/plate, 17k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Version Control Strategy?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,854 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.