Agent skill · software engineering · sickn33
cc-skill-continuous-learning
Turn a completed debugging session or repeated user correction into a small, evidence-backed procedure. Use for explicit requests to capture reusable lessons; does not automatically extract or save memories.
Why this skill is useful
This skill does not provide specific actionable knowledge or scripts beyond general development practices.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Continuous Learning from a Completed Session Capture one reusable lesson whose trigger, fix and verification can be explained without preserving a private conversation. The output is a reviewed procedure, not an automatic memory update. When to Use Use after a resolved failure, a repeated project-specific correction, or an explicit request to save what was learned. Skip one-off typos, unresolved guesses, transient provider outages and lessons already covered by project documentation. A long session alone does not make a lesson reusable. Inputs and prerequisites An authorized session summary or transcript, affected code or configuration, and the command or observation that confirmed the fix. The scope of the lesson: this repository, this tool version, or a more general procedure. An existing authorized documentation destination. If saving was not requested, return a draft in the conversation; do not update user memory, install skills, or modify agent configuration automatically. The optional session-length helper requires Bash and Python 3. Its only setting is minsessionlength in config.json. Procedure 1. Identify the failed assumption and final observed behavior. Keep unsuccessful hypotheses separate from the verified cause. 2. Check the current source and test result. A remembered fix that was never exercised stays an open hypothesis. 3. State a narrow trigger and prerequisites. Include the runtime or tool version when the fix depends on it. 4. Write the smallest sequence that reproduces the diagnosis and verifies the repair. Include an expected result and a counterexample where the procedure should not be used. 5. Remove secrets, user names, absolute personal paths, private messages and unrelated repository details. Prefer a minimal synthetic example to copying a transcript. 6. Compare with existing instructions. Amend an existing project note when authorized instead of creating another overlapping skill. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/cc-skill-continuous-learning--3663f5