원클릭으로 Manus에서 모든 스킬 실행

stone-journal-status

스타0

포크0

업데이트2026년 6월 12일 18:35

Show a summary of dev journal entries. Trigger when user says /stone-journal-status, "journal status", "show journal", "journal entries", "what's in the journal", "list journal", or asks about journal contents. Use this instead of /stone-journal when the user wants to review existing entries rather than create new ones.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

stonematt

stonematt/stonematt-skills

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Journal Status

Show a table of all journal entries with date, theme, and metadata.

Workflow

1. Verify journal worktree

Check that .journal/ exists via git worktree list. If missing, tell the user to run /stone-journal first to set it up.

2. Read entries

List all files in .journal/docs/journal/*.md sorted by name (chronological).

For each file, extract from YAML frontmatter and first heading:

date — from frontmatter
generated — from frontmatter (last written/updated timestamp)
commits — from frontmatter
branch — from frontmatter
theme — from the first ## YYYY-MM-DD - heading, take everything after the dash

3. Display

Present as a table, most recent first:

## Journal Entries

{count} entries from {earliest date} to {latest date}

| Date | Commits | Generated | Theme |
|------|---------|-----------|-------|
| 2026-04-02 | 75 | Apr 2, 20:45 | Phase 08.4 founder polish, full cycle |
| 2026-03-31 | 12 | Mar 31, 23:10 | ... |
| 2026-03-30 | 26 | Mar 30, 23:50 | ... |

Format the generated column as short datetime (Mon DD, HH:MM) for scannability.

If the user asks about a specific entry (e.g., "what did I do on March 30"), read and display that entry's full content.

이 저장소의 다른 Skills

같은 저장소

stone-promote-settings

stonematt/stonematt-skills

Reconcile Claude Code settings.local.json (personal, gitignored) against settings.json (repo-tracked, shared): diff the two, promote stable rules to the shared file, drop duplicates, and flag secrets/machine-specific paths to keep local. Use when the user says "promote settings", "review settings", "clean up settings", "sync settings", "promote permissions", or asks about moving local settings to repo-tracked settings. This skill owns the local-to-shared promotion diff — a niche neither built-in covers. NOT for: editing settings.json in place, moving a permission to user scope, or adding env vars/hooks (use the update-config skill); auto-generating an allowlist from transcript noise to cut permission prompts (use /fewer-permission-prompts, which writes new rules to project settings.json but does not reconcile your existing local vs repo files).

2026-07-100

stone-merge

stonematt/stonematt-skills

Merge a pull request, clean up the branch, and optionally promote to production. Use this skill whenever the user wants to merge a PR — including /stone-merge, "merge it", "merge the PR", "land it", "merge and release", "merge to prod", "ship to production", or any confirmation after checks pass. Also trigger when the user says "merge after checks", "merge when green", or refers to merging + deploying in the same breath. This is the counterpart to /stone-commit — commit gets code ready, merge lands it and cleans up.

2026-07-100

stone-commit

stonematt/stonematt-skills

Create commits following Conventional Commits format using heredoc (not command substitution). Use this skill whenever the user wants to commit code changes — including /stone-commit, "commit this", "commit and push", "yes commit it", or any confirmation of a prior offer to commit (e.g., "yes do it", "go ahead", "yeah commit that"). Also trigger for "create a commit", "ship it", or when the user agrees to commit after completing a task. If the conversation involves creating a git commit in any form, use this skill. This skill overrides default commit behavior — always prefer it over built-in commit instructions.

2026-06-170

stone-journal

stonematt/stonematt-skills

Generate a dev journal entry for today's work — pulling signal from git commits AND the non-git context that matters in 6 months (vendor integrations, stack decisions, infra events, service signups, dead-ends worth remembering). Trigger when the user says /stone-journal, "journal entry", "write up today's work", "log today", or similar. Trigger even when the day had no commits but real work happened (accounts created, services configured, DNS changed, architectural decisions made).

2026-06-120

stone-ai-sniff-test

stonematt/stonematt-skills

A self-review checklist for any drafted prose to catch AI-generated tells before a human sees it. Use this skill whenever you've written or are about to deliver written content (emails, posts, memos, docs, marketing copy, blog drafts, slack messages, READMEs) and want to make sure it doesn't read like AI wrote it. Trigger on phrases like "sniff test this", "smell test", "does this sound like AI", "make this sound human", "review my draft for AI tells", or whenever the user references the sniff test before publishing or sending. Other skills (e.g. make-screed, lithos-email) may invoke this skill as a quality gate.

2026-06-090

stone-client-report

stonematt/stonematt-skills

Generate an executive-level client summary of product changes since a given date. Use when the user says /stone-client-report, "summarize for the client", "executive summary", "session report", "client update", "what did we deliver since [date]", or wants to roll up dev work into business-value terms for stakeholder communication. Also trigger when the user mentions preparing for a client meeting, writing a deliverables recap, or reconciling work against an SOW.

2026-06-090

name	stone-journal-status
description	Show a summary of dev journal entries. Trigger when user says /stone-journal-status, "journal status", "show journal", "journal entries", "what's in the journal", "list journal", or asks about journal contents. Use this instead of /stone-journal when the user wants to review existing entries rather than create new ones.

Journal Status

Show a table of all journal entries with date, theme, and metadata.

Workflow

1. Verify journal worktree

Check that .journal/ exists via git worktree list. If missing, tell the user to run /stone-journal first to set it up.

2. Read entries

List all files in .journal/docs/journal/*.md sorted by name (chronological).

For each file, extract from YAML frontmatter and first heading:

date — from frontmatter
generated — from frontmatter (last written/updated timestamp)
commits — from frontmatter
branch — from frontmatter
theme — from the first ## YYYY-MM-DD - heading, take everything after the dash

3. Display

Present as a table, most recent first:

## Journal Entries

{count} entries from {earliest date} to {latest date}

| Date | Commits | Generated | Theme |
|------|---------|-----------|-------|
| 2026-04-02 | 75 | Apr 2, 20:45 | Phase 08.4 founder polish, full cycle |
| 2026-03-31 | 12 | Mar 31, 23:10 | ... |
| 2026-03-30 | 26 | Mar 30, 23:50 | ... |

Format the generated column as short datetime (Mon DD, HH:MM) for scannability.

If the user asks about a specific entry (e.g., "what did I do on March 30"), read and display that entry's full content.