القائمة
Extract actionable insights from completed coding sessions. Use when a session completes to capture learnings for future sessions.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/oimiragieo/agent-studio --skill insight-extractionيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Agent frontmatter enhancements — disallowedTools, mcpServers scoping, fork_eligible field
Context management — pre-compact persistence, threshold alignment, microcompact/circuit breaker detection
Hook enhancements — updatedInput for bash safety prefixes, suppressOutput for verbose blocks, denial-based routing feedback
| name | insight-extraction |
| description | Extract actionable insights from completed coding sessions. Use when a session completes to capture learnings for future sessions. |
| version | 1.1.0 |
| model | sonnet |
| invoked_by | both |
| user_invocable | true |
| tools | ["Read","Write","Bash","Glob","Grep"] |
| best_practices | ["Extract ACTIONABLE knowledge, not logs","Every insight should help future sessions do something better","Be specific about files, patterns, and gotchas"] |
| error_handling | graceful |
| streaming | supported |
| source | community |
| verified | true |
| lastVerifiedAt | "2026-02-22T00:00:00.000Z" |
| trust_score | 100 |
| provenance_sha | 33afe5ee90a44df9 |
Analyze completed coding sessions and extract structured learnings for the memory system. Insights help future sessions avoid mistakes, follow established patterns, and understand the codebase faster.
Core principle: Extract ACTIONABLE knowledge, not logs. Every insight should help a future session do something better.
Always:
Exceptions:
NO SESSION END WITHOUT INSIGHT EXTRACTION FOR NON-TRIVIAL WORK
Non-trivial sessions should capture learnings before context is lost.
To extract insights, you need:
# Get the diff of changes
git diff HEAD~1 --stat
git diff HEAD~1
# Get commit message
git log -1 --pretty=format:"%s%n%n%b"
# Get list of modified files
git diff HEAD~1 --name-only
For each modified file, extract:
Good example:
{
"path": "src/stores/terminal-store.ts",
Bad example (too vague):
{
"path": "src/stores/terminal-store.ts",
"purpose": "A store file",
"changes_made": "Added some code",
"patterns_used": [],
"gotchas": []
}
Only extract patterns that are reusable:
Good example:
{
"pattern": "Use e.stopPropagation() on interactive elements inside containers with onClick handlers",
"applies_to": "Any clickable element nested inside a parent with click handling",
"example": "Terminal.tsx header - dropdown needs stopPropagation to prevent focus stealing"
}
Must be specific and actionable:
Good example:
{
"gotcha": "Terminal header onClick steals focus from child interactive elements",
"trigger": "Adding buttons/dropdowns to Terminal header without stopPropagation",
"solution": "Call e.stopPropagation() in onClick handlers of child elements"
}
Capture the learning from success or failure:
This helps future sessions learn from past attempts.
Specific, actionable advice for future work:
Good: "When adding more controls to Terminal header, follow the dropdown pattern in this session - use stopPropagation and position relative to header"
Bad: "Write good code" or "Test thoroughly"
Create the structured insight output:
# Session Insights: [Task Name]
## Date
[timestamp]
## Task
[Description of what was being implemented]
## Outcome
[SUCCESS/FAILURE]
## File Insights
### [file-path]
- **Purpose**: [what this file does]
- **Changes**: [what was changed and why]
- **Patterns**: [patterns used]
- **Gotchas**: [things to watch out for]
## Patterns Discovered
### [Pattern Name]
- **Pattern**: [description]
- **Applies to**: [when to use]
- **Example**: [file or code reference]
## Gotchas Discovered
### [Gotcha Name]
- **Issue**: [what to avoid]
- **Trigger**: [what causes it]
- **Solution**: [how to handle]
## Approach Analysis
### What Worked
[Description of successful approach]
### What Failed (if applicable)
[Description of failed approaches and why]
### Alternatives Tried
[List of other approaches attempted]
## Recommendations for Future Sessions
1. [Specific recommendation 1]
2. [Specific recommendation 2]
Save to .claude/context/memory/learnings.md (append).
If the diff is very small or empty:
If the session failed:
Before completing insight extraction:
Why it's wrong: "Fixed the bug" helps no one.
Do this instead: "Fixed race condition in useEffect by adding cleanup function. Pattern: always return cleanup from async effects."
Why it's wrong: "Test your code" is not actionable.
Do this instead: "Run npm test src/stores after changing store logic - the tests catch state management bugs."
Why it's wrong: Future sessions won't understand why.
Do this instead: Include file paths, function names, and specific scenarios.
This skill works well with:
[CODE], [WORKFLOW], [SECURITY], etc.) — untagged insights are effectively invisible to agents searching by domain.| Anti-Pattern | Why It Fails | Correct Approach |
|---|---|---|
| Recording activity ("implemented auth") instead of learnings | Agents can reconstruct history from git; they cannot reconstruct tacit knowledge | Record "why" and "gotcha": "Fiber's CSRF middleware must be before route registration, not after" |
| Skipping deduplication check | Duplicate entries inflate memory size and confuse retrieval | grep -i "keyword" learnings.md before appending; update existing entry if found |
| Vague insights without file/function context | Future sessions can't locate or apply the insight | Include concrete path: "In .claude/hooks/routing/routing-guard.cjs line 47: exit 0 on parse error" |
| Extracting only at session end | Long sessions lose early context; critical gotchas forgotten | Extract after each significant task completion, not just at session boundary |
| Storing insights only in task metadata | Task metadata is not read by future sessions or agents | Always write to .claude/context/memory/learnings.md with tagged format |
Before starting:
Read .claude/context/memory/learnings.md
After completing:
.claude/context/memory/learnings.md.claude/context/memory/issues.md.claude/context/memory/decisions.mdASSUME INTERRUPTION: If it's not in memory, it didn't happen.