How do I install the Self Commenting skill?

Run npx skillmds@latest add app-builders-club/self-commenting in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Self Commenting safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Self Commenting?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Self Commenting free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Self Commenting?

app-builders-club (@app-builders-club) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Self Commenting by app-builders-club

Name: Self Commenting
Author: app-builders-club

Self Commenting

AI-native code commenting system with grep-searchable AICODE-* markers for cross-session memory. Use when: working with code files, leaving notes for future sessions, breaking down complex tasks, documenting non-obvious logic, recording bug fixes. Triggers: start coding session, edit code, complex logic, leave note, todo for later, debug session, bug fix, AICODE markers, self-commenting.

app-builders-club b75520b 2 files · 5.0 KB Updated Sep 17, 2026

File contents

Self-Commenting

Long-term memory layer in code using grep-searchable AICODE-* markers.

Process

SCAN → WORK → ANNOTATE

Step 1: Scan

Before modifying any file, find existing markers:

grep -rn "AICODE-" <file-or-directory>

Read markers to understand previous context and pending tasks.

Step 2: Work

Edit code normally.

Step 3: Annotate

Add markers for cross-session memory:

AICODE-NOTE — critical implementation details
AICODE-TODO — pending tasks to complete
AICODE-FIX — non-trivial bug solutions (problem → cause → fix)

See references/conventions.md for format, language syntax, and examples.

Decision Rules

Add AICODE-NOTE when:

Non-obvious algorithm or approach
External API constraints
Complex state management
Integration quirks

Add AICODE-TODO when:

Task out of current scope
Needs more information
Depends on other work

Add AICODE-FIX when:

Bug solution was non-trivial
Root cause wasn't obvious
Similar bugs might occur elsewhere

Skip markers when:

Code is self-explanatory
Standard pattern usage
Trivial one-line fix

Session Workflow

Start: grep -rn "AICODE-" src/

Before debugging: Check for similar AICODE-FIX in codebase

End: Add TODO for incomplete work, NOTE for key decisions, FIX for solved bugs

Frequently asked questions