‹ 首页

prompt-versioning

@owl-listener · 收录于 5 天前 · 上游提交 1 个月前

Managing prompt iterations, testing changes, and tracking what works.

场景提示词迭代效果对比版本回溯

适合你，如果你经常调整提示词并需要记录哪些改动有效

/ 下载安装
https://github.com/owl-listener/ai-design-skills/tree/main/claude-plugin/prompt-architecture/skills/prompt-versioning ↗
/ 通过 npx 安装 校验哈希
npx oh-my-skill add owl-listener/ai-design-skills/prompt-versioning
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- owl-listener/ai-design-skills/prompt-versioning
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify owl-listener/ai-design-skills/prompt-versioning
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
144GitHub stars
~548上下文体积 · 单文件
索引托管

怎么用

商店整理自技能原文 · 版本 f41b650 · 表述以原文为准
它做什么

Claude 会引导你像管理代码一样管理提示词，包括版本控制、测试、审查和部署，并帮助你跟踪每次修改的效果。

什么时候触发

当你询问如何管理提示词版本、测试提示词改动、或回滚到旧版本时触发。

装好后可以这样说
Claude 会建议提交说明格式
Claude 会指导你如何做A/B测试
Claude 会解释回滚流程
技能原文 SKILL.md作者撰写 · MIT · f41b650

Prompt Versioning

Prompts are code. They should be versioned, tested, reviewed, and deployed with the same rigor as software. Treating prompts as casual text that anyone can edit leads to quality regressions, inconsistent behavior, and debugging nightmares.

Why Version Prompts
  • Accountability: Know who changed what and when
  • Rollback: Revert to a previous version when a change causes problems
  • Testing: Compare performance of different versions
  • Collaboration: Multiple people can work on prompts without overwriting each other
  • Audit trail: Understand how the prompt evolved and why
Versioning Practices
  • Source control: Store prompts in version control (Git, etc.), not in application configuration
  • Meaningful commits: Each change should explain what was changed and why
  • Change categories: Classify changes as bug fixes, improvements, new features, or experiments
  • Review process: Prompt changes should be reviewed before deployment, like code reviews
  • Semantic versioning: Major changes (behavioral shift), minor changes (new capability), patches (bug fixes)
Testing Prompt Changes

Before deploying a prompt change:

  • Regression testing: Run the golden test set against the new version. Did anything get worse?
  • Targeted testing: Test the specific scenario the change was designed to improve
  • Edge case testing: Test edge cases related to the change
  • A/B testing: For significant changes, run both versions in production and compare
  • User testing: For major persona or behavioral changes, test with real users
Prompt Change Management
  • Staging environment: Test prompt changes in a non-production environment first
  • Gradual rollout: Deploy to a percentage of users, monitor, then expand
  • Feature flags: Toggle prompt features on and off without deployment
  • Monitoring: Watch quality metrics closely after any prompt change
  • Rollback plan: Always know how to revert if the change causes problems
Common Versioning Mistakes
  • Untracked changes: Editing prompts in production without recording the change
  • Untested changes: Deploying changes without testing against known scenarios
  • Big bang changes: Changing many things at once, making it impossible to know what helped or hurt
  • Lost context: Changing a prompt without understanding why the previous version was written that way
Design Artefacts
  • Prompt repository structure
  • Change review checklists
  • Testing protocols per change type
  • Deployment and rollback procedures
  • Prompt change request templates
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。
…