notes

A command and tldr for managing notes and tasks in the shell.

Updated May 9, 2026
One-click install
npx skills add https://github.com/PetitChu/holocron --skill notes-petitchu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notes
Source: https://github.com/PetitChu/holocron/tree/main/skills/notes
Command: npx skills add https://github.com/PetitChu/holocron --skill notes-petitchu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you capture and organize writing issues and ideas without losing them, separating quick inline chapter triage from durable project-level decisions.

Core Features & Use Cases

  • Inline Editing Notes (Tier 1): Collects %%NOTE:%%, %%EDIT:%%, %%CHECK:%%, and %%CUT:%% markers from chapter prose with chapter name and line numbers so you can review and process them systematically.
  • Project Notes (Tier 2): Maintains a persistent notes.md scratchpad with dated bullets under Ideas, Todos, World Questions, and Remember, enabling ongoing planning that doesn’t clutter chapters.
  • Workflow Controls: Supports listing everything (--list), step-by-step processing (--process), and cleaning up chapter markers (--clear) while leaving project notes intact.
  • Batch Management: Scans chapters for marker patterns, groups by type, and renders a combined view (project notes first, then inline markers) for the dashboard Workshop tab.

Quick Start

Run /holocron:notes --list to view all project notes and every inline NOTE/EDIT/CHECK/CUT marker currently present in your chapters.

Frequently Asked Questions about notes

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

FAQPage Schema
How do I extract inline editing notes from chapter files for story revision?

To extract inline editing notes, the Skill scans chapter prose for `NOTE`, `EDIT`, `CHECK`, and `CUT` markers, grouping them by type and line number. This organizes writing triage by collecting chapter names and line numbers so you can process issues systematically.

What is the best way to organize writing triage and continuity checks across multiple chapters?

Organizing writing triage is handled by maintaining a persistent project-level `notes.md` scratchpad with dated bullets under Ideas, Todos, World Questions, and Remember. This separates quick inline chapter triage from durable project-level planning.

How do I list all planned edits and cuts in my writing project?

You can list all planned edits and cuts by running the `--list` command. This workflow control renders a combined view that displays persistent project notes first, followed by every inline marker currently present in your chapters.

Can I clean up inline markers from chapters without deleting my project notes?

Yes, you can clean up inline markers without affecting project notes by using the `--clear` command. This workflow control removes chapter markers while leaving the persistent `notes.md` scratchpad completely intact.

Does this writing triage tool require any dependencies to scan markers?

No, this writing triage tool requires zero dependencies to scan markers. It independently searches chapter files for marker patterns and creates a `notes.md` template from scratch when missing.