Appends durable non-obvious findings to a repository journal using a canonical template.
npx skills add https://github.com/islamu-ngo/Event --skill finding-islamu-ngo
Please help me install this Agent Skill. Skill: finding Source: https://github.com/islamu-ngo/Event/tree/main/.agents/skills/finding Command: npx skills add https://github.com/islamu-ngo/Event --skill finding-islamu-ngo
dev/_journal/journal.md using the canonical FINDING_TEMPLATE.md format with date prefix, root cause, resolution, and references. - Recording Criteria Enforcement: Defines clear rules for what qualifies as a durable finding (non-obvious, durable, reusable) and what should be excluded. - Promotion Workflow: Integrates with PROMOTION_RULES.md so frequently referenced entries can graduate to quick references, rules, or governance docs. - Use Case: After debugging why a test suite fails only in CI due to a timezone assumption, record the root cause with file:line anchors so the next engineer does not rediscover it from scratch. ## Quick Start Record a durable finding about the timezone-dependent test failure we just diagnosed by appending it to the development journal.High-intent search queries and answers about installing and using this skill.
Copy the block from dev/_journal/FINDING_TEMPLATE.md, fill in fields like date prefix, root cause, and resolution, then append it to the end of dev/_journal/journal.md. Leave exactly one blank line between entries and never insert entries mid-file.
A finding qualifies when it is non-obvious (not inferable from code alone), durable (still true months later), and reusable (valuable to other contributors). Routine progress notes, refactoring logs, and facts already documented elsewhere should not be recorded.
Skip recording when the fact is already covered in QUICK_REFERENCE, GOVERNANCE, an existing skill, or a rule—link to it instead. Also avoid logging step-by-step implementation details, personal opinions, or trivial observations like basic tool usage.
No, journal entries are append-only and chronological. Instead of deleting, annotate outdated entries with a promotion note such as 'promoted to X' as described in PROMOTION_RULES.md.
An entry becomes a promotion candidate when it has been referenced by at least two subsequent entries, cited in a PR review, or generalizes beyond its original feature. The PROMOTION_RULES.md file defines the five possible destination types.
gaos6eDiagnose root causes of bugs and service failures through evidence-based hypothesis testing.
AgenticFlowXCapture development discussions and record decisions into ADRs or feature specifications.
TheBushidoCollectiveEstablish bidirectional links between code and documentation with multiple link formats.
shipsAutomates commit-message generation and validates code quality, delivering accurate Git commit summaries with Trello integration for effortless CI/CD workflows.