Back to Details

skill-loop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

skill-loop

skill-loop

Use this skill for two cases:
  • bootstrap skill-loop into a repository with a GitHub issue workflow
  • write, simplify, or migrate 
    skill-loop.yml
本技能适用于以下两种场景：
  • 在带有GitHub issue工作流的代码仓库中初始化skill-loop
  • 编写、简化或迁移
    skill-loop.yml
    文件

Modes

模式

  • GitHub bootstrap: read 
    references/github-init.md
  • YAML authoring or migration: read 
    references/yaml-authoring.md
    , then follow the selected pattern reference only
  • GitHub初始化：阅读
    references/github-init.md
  • YAML编写或迁移：阅读
    references/yaml-authoring.md
    ，之后仅遵循所选的模式参考

Working style

工作风格

  • Keep the generated setup minimal.
  • Prefer 
    tracker.repo
    plus a small 
    skills:
    graph.
  • Prefer an 
    issue-check
    entrypoint that uses 
    gh
    to choose the next ready issue and complete the minimum setup before planning.
  • Treat YAML authoring as pattern selection first, then concrete authoring.
  • Reuse templates from 
    assets/
    instead of writing large starter files from scratch.
  • Default to 
    .claude/skills/
    for generated starter skills unless the repository already uses another skill directory.
  • 保持生成的设置尽可能简洁。
  • 优先使用
    tracker.repo
    搭配小型
    skills:
    图谱。
  • 优先选择使用
    gh
    工具的
    issue-check
    入口点，在规划前选择下一个待处理的issue并完成最小化设置。
  • YAML编写应先选择模式，再进行具体编写。
  • 复用
    assets/
    目录下的模板，而非从头编写大型启动文件。
  • 生成的启动技能默认存放于
    .claude/skills/
    目录，除非仓库已使用其他技能目录。

Expected outputs

预期输出

  • create or update 
    skill-loop.yml
  • select the right workflow pattern before drafting YAML
  • create starter skills only when the selected pattern actually needs them
  • explain the execution flow in terms of the chosen pattern
  • 创建或更新
    skill-loop.yml
    文件
  • 在起草YAML前选择合适的工作流模式
  • 仅在所选模式确实需要时才创建启动技能
  • 结合所选模式解释执行流程

Validate

验证