القائمة
Aggregate journal entries to surface patterns — recurring blockers, most-modified files, effective tools, and team velocity trends. Use for retrospectives, standups, or understanding project health.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | summary |
| description | Aggregate journal entries to surface patterns — recurring blockers, most-modified files, effective tools, and team velocity trends. Use for retrospectives, standups, or understanding project health. |
Analyze the journal to surface patterns across multiple sessions. Produces aggregate insights rather than individual entries — what keeps going wrong, what keeps working, where the effort is concentrated.
Announce at start: "Analyzing journal for patterns."
Reads from .claude/journal.jsonl in the project root.
/field-notes:summary # last 7 days (default)
/field-notes:summary week # last 7 days
/field-notes:summary month # last 30 days
/field-notes:summary all # everything
Count entries by type:
Activity (last 7 days):
work: 12 entries
bug-fix: 4 entries
refactor: 2 entries
exploration: 3 entries
review: 1 entry
audit: 1 entry
─────────────────────
Total: 23 entries
Files that appear most frequently across entries:
Most Modified Files:
1. packages/server/src/server/routes/api.ts (8 entries)
2. packages/core/src/core/context.ts (5 entries)
3. packages/frontend/src/components/ActivityLog.tsx (4 entries)
These are churn indicators — files touched repeatedly may need refactoring or better test coverage.
Extract and deduplicate blockers from entries:
Recurring Blockers:
- "Mock pollution in tests" (appeared 3 times)
- "Rate limiter config unclear" (appeared 2 times)
- "SSE connection timeout" (appeared 2 times, resolved 2026-03-27)
Resolved blockers (appear in later entries as fixes) are marked.
Aggregate the insights and wouldDoDifferently fields:
Top Insights:
- Two-stage review (spec + quality) catches different failure modes (3 mentions)
- Check installed package version before reading docs (2 mentions)
- Worktree delegation prevents context pollution (2 mentions)
Recurring "Would Do Differently":
- "Run full test suite earlier" (3 mentions)
- "Read existing tests before writing new ones" (2 mentions)
Which zen skills are used most:
Skills Usage:
zenflow:dispatch 8 sessions
zenflow:check-work 8 sessions
zenflow:collab 5 sessions
zenflow:bug-fix 4 sessions
zenflow:plan 3 sessions
zenflow:idea 1 session
## Journal Summary — last 7 days (23 entries)
### Activity
[breakdown by type]
### Hot Files
[top 5 most-modified files]
### Recurring Blockers
[deduplicated, with resolution status]
### Insights
[aggregated patterns from insights + wouldDoDifferently]
### Skills
[usage counts]
### Health Signals
- Bug-fix ratio: 17% (4/23) — [healthy < 25%]
- Workaround ratio: 9% (2/23) — [healthy < 15%]
- Blocker-free sessions: 78% (18/23)
Quick indicators derived from the data:
| Signal | Healthy | Warning | Unhealthy |
|---|---|---|---|
| Bug-fix ratio | < 25% | 25-40% | > 40% |
| Workaround ratio | < 15% | 15-30% | > 30% |
| Blocker-free sessions | > 70% | 50-70% | < 50% |
| Repeat blocker rate | < 10% | 10-25% | > 25% |
These are rough heuristics, not hard rules. A spike in bug fixes after a big feature is normal.
Discover files with trigger_phrase and/or refresh frontmatter, let the user choose which to schedule for periodic re-injection via CronCreate. Prevents behavioral drift by keeping core rules and goals fresh in context.
Write trigger phrases from .claude/triggers.json into file frontmatter as model-scoped trigger_phrase fields. Bridges trigger generation (scan) with scheduled injection (zenflow:schedule).
Build a GitHub issue into a PR. User-launched with an issue number — reads the issue, confirms with user, creates branch, implements against acceptance criteria, runs verification, and opens a PR. Every decision surfaces via AskUserQuestion.
Collaborative working session — you and the user are a team exploring, researching, and planning together. When implementation work is needed, create well-structured GitHub issues. The user launches Builder agents to implement and Reviewer agents to verify.
Shed accumulated context mid-session. Writes a knowledge handoff document capturing session state, decisions, observations, and behavioral calibration, then guides the user through /clear and resumption.
Runtime verification using Playwright MCP + proof artifacts. Use when acceptance criteria mention UI behavior, when claiming runtime verification, or when independently verifying a PR's claims. Produces artifact-backed proof — screenshots, DOM snapshots — not prose claims.