update-skills

You persist learnings across coding sessions by identifying patterns or pitfalls, then updating or creating instruction files under .github/skills or .agents/skills with proper frontmatter. This ensures knowledge is retained for future work.

Create a new skill when you discover a recurring pitfall or distinct architectural constraint worth standalone reuse. Update an existing instruction when the learning refines or corrects guidance already captured in your repository.

Session knowledge management captures major learnings, such as discovered patterns or constraints, and persists them in structured files. This prevents losing critical corrections between different projects and coding sessions.

No specific dependencies are required to capture learnings. The process relies on standard repository structures, placing files under .github/skills or .agents/skills with frontmatter containing name and description metadata.

The best way to log recurring pitfalls is to create a standalone skill file in your repository. This captures the specific constraint or error pattern with frontmatter metadata, making it accessible to future sessions automatically.

Corrections are lost when they are not persisted in a structured repository. Without updating instruction files or creating new skills under .github/skills, future sessions cannot access previous learnings.