communicate

Category: Tools & Productivity | Uploader: yologdev | Downloads: 0 | Version: v1.0（Latest）

Write journal entries, respond to issues, and record learnings

Changelog: Source: GitHub https://github.com/yologdev/yopedia

Directory Structure

Current level: tree/main/.yoyo/skills/communicate/

📄 SKILL.md 1.4 KB

SKILL.md

---
name: communicate
description: Write journal entries, respond to issues, and record learnings
tools: [bash, write_file, read_file]
---

# Communication

## Journal Entries

Write at the top of .yoyo/journal.md after each session. Format:

```markdown
## YYYY-MM-DD HH:MM — [short title of what you did]

[2-4 sentences: what you tried, what worked, what didn't, what's next]
```

Rules:
- Be honest. If you failed, say so.
- Be specific. "Built ingest page" is boring. "Wired up URL fetching with readability extraction and markdown conversion" is interesting.
- Be brief. 4 sentences max.
- End with what's next.

## Issue Responses

Use `gh` CLI directly:

- **Comment:** `gh issue comment NUMBER --repo OWNER/REPO --body "YOUR_MESSAGE"`
- **Close:** `gh issue close NUMBER --repo OWNER/REPO`

Decide for each issue:
- Fixed → comment what you did, close
- Partial → comment with update, keep open
- Won't fix → explain why, close
- No progress → skip (silence > noise)

Keep responses to 3 sentences max. Be direct and honest.

## Learnings

After journal and issue responses, reflect: what did this session teach you?

**Admission gate:**
1. Is this genuinely novel?
2. Would this change how you work in a future session?
If both aren't yes, skip it.

Format in .yoyo/learnings.md:
```markdown
## [Short insight]
**Context:** [what happened]
**Takeaway:** [reusable insight]
```

Don't force it — not every session produces a lesson.

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

communicate

Directory Structure

SKILL.md

Report

Notice