extract-approach
SkillDocs & knowledgeUse when a non-trivial problem has just been solved (bug fixed after debugging, tricky implementation completed, blocker resolved) and the session is about to move on. A solution without its learnings note is unfinished work.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the extract-approach skill
What this skill tells your AI
The instructions your AI receives, as published by atcoder-novisteps/atcodernovisteps in .agents/skills/extract-approach/SKILL.md and read by ahel’s review.
Extract the approach from the just-solved problem into a learnings note for: $ARGUMENTS
Skip when: trivial fixes (typo, rename, config tweak), dependency bumps, or the insight is already covered by docs/guides/agent-rules/ or the task's plan.md.
- Identify the problem — the symptom from this session and what made it non-trivial; multiple candidates → confirm which one with AskUserQuestion
- Extract — 問題 / 有効だったアプローチ / ハマった点 / 教訓 only; apply the extraction and abstraction rules in instructions.md
- Write the note —
docs/dev-notes/YYYY-MM-DD/{task-name-en}/learning.md; naming and format rules in instructions.md - Escalate durable rules — propose target file and exact wording for project-wide conventions; do not apply without user confirmation
Signals
- GitHub stars
- 67
- Forks
- 10
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
extract-approach- Source
- github.com/atcoder-novisteps/atcodernovisteps