Conversation
…tions, and pipeline integration - Add 'When to save' section with clear rules for agents - Add setup section with wrapper path and DB config - Add annotation conventions: actor names, confidence guidelines, highlight vs lowlight - Add content pipeline integration workflow (save → ingest → annotate → link to content-board) - Clarify that linkledger wrapper works from any directory
|
Review findings from my pass:
Everything else in the PR (when-to-save, annotation conventions, pipeline integration) is a solid improvement. |
- Remove hardcoded /opt/homebrew path assumption - Document both wrapper and repo-local invocation modes - Clarify LINKLEDGER_DB_PATH behavior and cwd default
|
Good catches — both fixed in 2504a1e:
|
gdiab
left a comment
There was a problem hiding this comment.
Re-review complete. The previously reported issues are resolved:
- Setup guidance is now portable (wrapper is conditional, repo-local fallback documented).
- DB path behavior is now aligned with project defaults and LINKLEDGER_DB_PATH override guidance.
No additional blocking findings from this pass.
What
Enhances the bundled agent skill (
skills/linkledger-cli-agent/SKILL.md) to make it more useful for sub-agents and multi-agent workflows.Changes
agent:<name>), confidence scale guidelines (0.5–1.0 with use-case table), highlight vs lowlight guidance, when to pinWhy
The existing skill covers the how (command syntax) but not the when or why. Sub-agents doing research tasks need opinionated guidance on save discipline, annotation quality, and how LinkLedger fits into a broader content pipeline.
Closes #13 partially (documents the wrapper workaround in the setup section).