self-commenting
/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.
- Author
- petbrains ↗
- Repository
- mvp-builder ↗
- Licence
- MIT
- Last repository change
- 06.09.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 06.09.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- Process
- Step 1: Scan
- Step 2: Work
- Step 3: Annotate
- Decision Rules
- Session Workflow
SKILL.md preview
--- name: self-commenting description: "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." --- # 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: ```bash 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
Files in this package (2)
- SKILL.md 2 KB
- references/conventions.md 3 KB
Versions
The database has no other skills named self-commenting.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 386cd100f060 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100code-analyzer
Comprehensive codebase analysis for building mental model of project structure, dependencies, and implementation context. Use when needing to: (1) Understand project architecture before review or documentation, (2) Find dependencies and shared modules, (3) Trace execution paths… - 100self-explanatory-code-commenting
Guidelines for GitHub Copilot to write comments to achieve self-explanatory code with less comments. Examples are in JavaScript but it should work on any language that has comments. Triggers on: ** - 80Global Commenting
Write self-documenting code with clear naming and structure, adding minimal, evergreen comments only when necessary to explain complex logic. Use this skill when writing or reviewing any code that might need comments. When refactoring code to make it more self-explanatory…