Append structured entries to project journal markdown files with lint validation.
npx skills add https://github.com/jellyrock/jellyrock --skill log-jellyrock
Please help me install this Agent Skill. Skill: log Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/log Command: npx skills add https://github.com/jellyrock/jellyrock --skill log-jellyrock
Manually maintaining multiple structured project journals (decisions, followups, signals, running work) across separate markdown files with unique formatting rules is tedious, error-prone, and leads to inconsistent record-keeping that breaks downstream tooling like staleness banners and audit trails.
Invoke the log skill with the entry type and your content to automatically append the correctly formatted entry to the appropriate project journal file.
High-intent search queries and answers about installing and using this skill.
Automated journal logging appends entries to architectural decisions, open followups, upstream version signals, and in-flight work cursors with a single command. It routes content to the correct file, matches existing formatting, and runs lint validation to eliminate manual errors.
Capturing architectural decisions is handled through agent-gated significance classification that routes qualifying entries directly to ADR files. This gating mechanism prevents decision-log creep by ensuring only significant decisions are recorded, while routine notes bypass the gate.
Automatic lint validation runs after every journal write to validate the schema and staleness metadata of project journals. This ensures downstream tooling like staleness banners and audit trails continue to function correctly without manual consistency checks.
Tracking open followups, upstream version signals, and in-flight work cursors is supported natively within the same logging workflow. Each entry type is mechanically appended to its respective structured markdown file, maintaining unique formatting rules across all four journal types.
Manually maintaining separate markdown journals is error-prone and leads to inconsistent record-keeping that breaks downstream tooling. Automated logging enforces schema compliance and significance gating to preserve the integrity of staleness banners and audit trails.
Agent-gated significance classification is required specifically for architectural decision entries to prevent decision-log creep. Routine captures like followups and signals use direct mechanical appends, bypassing the gate to streamline standard project logging.
jellyrockCloses shipped-work journal entries in JellyRock progress and backlog markdown files.
flonatConsolidates MEMORY.md files by pruning duplicates, merging overlaps, and removing stale knowledge.
phuonghxAutomate linting, formatting, type checking, and security audits for Node.js/TypeScript and Python codebases.
desirecoreCreate, edit, and organize Markdown documents for reports and notes.
