markdown-toc
Extract a Markdown heading tree with line numbers before editing or integrating notes. Use when you need to inspect a long Markdown file quickly and choose the best insertion point instead of editing blind.
소스 정보
- 저장소
- huangruiteng/CS-Notes
- 최근 소스 활동
- 2026년 10월 2일 07:39
- 감지된 SKILL.md 언어
- 영어
- 스타
- 4,002
- 포크
- 482
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
3 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- markdown-toc
- description
- Extract a Markdown heading tree with line numbers before editing or integrating notes. Use when you need to inspect a long Markdown file quickly and choose the best insertion point instead of editing blind.
# Markdown TOC
## Use this skill when
Use this skill before editing a long Markdown file, especially when you need to:
- inspect the heading structure quickly;
- choose the best section for new content;
- avoid creating redundant sections; or
- review nearby lines before patching a note.
## Quick start
Resolve `{baseDir}` to this skill’s actual directory, then run the bundled script. It reports ATX (`#`) headings, excluding fenced code; Setext headings and full Markdown parsing are outside its scope:
```bash
python3 "{baseDir}/scripts/extract_toc.py" /absolute/path/to/file.md
```
In this repository, common targets include:
```bash
python3 "{baseDir}/scripts/extract_toc.py" Notes/Gourmet.md
python3 "{baseDir}/scripts/extract_toc.py" "Notes/AI-Agent-Product&PE.md"
```
## Workflow
1. Run the TOC script on the candidate file.
2. Read the returned heading tree and line numbers.
3. Open the most likely section neighborhood with `sed -n '<start>,<end>p'` or `nl -ba`.
4. Insert into an existing section when possible.
5. Create a new section only when the file truly lacks a clean landing spot.
## Output format
The script prints a compact tree like this:
```text
TOC
--------------------------------------------------
# Title (line 1)
## Section (line 20)
### Subsection (line 42)
```
GitHub에서 보기