返回 Skill 列表
extension
分类: 开发与工程无需 API Key

learning-loop

在代码探索或用户交互过程中捕捉到的新知识,这些新知识在上下文、记忆或代码库文档中并不存在。当Claude发现有关代码库、工具、工作流程或领域知识的新内容,并且这些新内容可能对未来会话有益时,应该调用此技能。

person作者: jakexiaohubgithub

Learning Loop

Log new knowledge discovered during work sessions that was not already documented in context, memories, or Markdown files in the codebase.

When to Use

Invoke this skill when discovering something new during:

  • Code exploration: Found undocumented behavior, hidden configuration, or implicit patterns
  • User interaction: User shared information not captured in existing documentation
  • Tool discovery: Learned about tools, commands, or workflows not previously documented
  • Domain knowledge: Gained understanding of business logic or domain concepts not in codebase docs

Do NOT invoke when:

  • The information is already in CLAUDE.md, rules, or other documentation
  • The learning is project-agnostic (general programming knowledge)
  • The information was explicitly provided in the current conversation context

How to Log

Run the logging script with the learning summary:

.claude/skills/learning-loop/scripts/log-learning.sh "<summary>"

Arguments

| Argument | Description | Example | | --------- | --------------------------------------- | -------------------------------------------- | | summary | Concise description of what was learned | "API rate limits are 100 req/min per tenant" |

Examples

# Learned about undocumented configuration
.claude/skills/learning-loop/scripts/log-learning.sh "Feature flags are stored in Redis, not the database"

# Discovered implicit pattern during exploration
.claude/skills/learning-loop/scripts/log-learning.sh "All background jobs use the BaseJob class from libs/jobs"

# User shared domain knowledge
.claude/skills/learning-loop/scripts/log-learning.sh "Tenant IDs starting with 'demo_' are test accounts"

Output

Learnings are appended to .claude/learning.yaml with timestamp:

- date: '2025-01-20T14:30:00Z'
  summary: 'Feature flags are stored in Redis, not the database'

Notes

  • Keep summaries concise but informative (1-2 sentences max)
  • Focus on actionable or context-critical information
  • The file is intended for periodic review to identify documentation gaps