self-commenting

Annotate code with grep-searchable AICODE-* markers for cross-session memory.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/akhmat-s/Bantadthong-Vibes --skill self-commenting-akhmat-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: self-commenting
Source: https://github.com/akhmat-s/Bantadthong-Vibes/tree/main/.claude/skills/self-commenting
Command: npx skills add https://github.com/akhmat-s/Bantadthong-Vibes --skill self-commenting-akhmat-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes references (resource) components.

What problem does it solve?

This Skill eliminates the frustration of losing context between coding sessions by embedding searchable markers directly in your code.

Core Features & Use Cases

  • Cross-Session Memory: Leave notes, todos, and bug fixes that persist across AI sessions.

Core Features & Use Cases

  • Grep-Searchable Markers: Use AICODE-* markers for notes, todos, and fixes that future AI sessions can instantly find and understand.

Quick Start

Scan the current file for existing AICODE markers to understand previous work.

Frequently Asked Questions about self-commenting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I keep code notes and context across multiple AI sessions?

Cross-session memory embeds searchable AICODE-* markers directly in your code—AICODE-NOTE, AICODE-TODO, and AICODE-FIX—so future sessions instantly retrieve context without losing notes between edits.

What's the best way to document non-obvious code behavior for future reference?

Use grep-searchable AICODE markers to annotate complex logic, bug fixes, and decisions inline. Future sessions grep for AICODE-* to find and understand previous work without manual searching.

How do I organize and locate code annotations across multiple files?

Grep tooling searches AICODE-* markers across files using the three-phase workflow: SCAN existing markers, WORK on edits, then ANNOTATE with new markers. Conventions.md defines marker usage patterns.

Can I use grep and jq to manage code memory markers in my workflow?

Yes. The Skill requires jq and grep tools to scan for, locate, and reference AICODE-* markers. Grep finds markers across files; jq processes structured marker data.

What markers should I use for todos, notes, and bug fixes?

Use AICODE-NOTE for context and observations, AICODE-TODO for pending work, and AICODE-FIX for bug corrections. Each persists across sessions and remains grep-searchable for retrieval.