Skip to content

Add Lore plugin to Plugins & Extensions#41

Open
yacb2 wants to merge 1 commit intojmanhype:mainfrom
yacb2:add-lore
Open

Add Lore plugin to Plugins & Extensions#41
yacb2 wants to merge 1 commit intojmanhype:mainfrom
yacb2:add-lore

Conversation

@yacb2
Copy link
Copy Markdown

@yacb2 yacb2 commented Apr 29, 2026

Adds Lore, a living knowledge graph for software projects, to the Plugins & Extensions table.

What it does: Captures business logic (modules, capabilities, flows, events, rules, decisions) as a typed graph backed by SQLite. Auto-invoked skills and slash commands let coding agents query and maintain it across sessions.

Distribution: Claude Code plugin marketplace. License: MIT.

Following the table format and contributing guidelines (single suggestion, period at end of description).

@qodo-code-review
Copy link
Copy Markdown

Review Summary by Qodo

Add Lore plugin to Plugins & Extensions documentation

📝 Documentation

Grey Divider

Walkthroughs

Description
• Adds Lore plugin entry to Plugins & Extensions table
• Describes living knowledge graph for software projects
• Includes features: typed graph, SQLite backend, skills
Diagram
flowchart LR
  README["README.md<br/>Plugins table"]
  LORE["Lore plugin entry<br/>yacb2/lore"]
  README -- "adds new row" --> LORE
Loading

Grey Divider

File Changes

1. README.md 📝 Documentation +1/-0

Add Lore plugin documentation entry

• Adds new table row for Lore plugin in Plugins & Extensions section
• Includes repository link, author (yacb2), and feature description
• Describes typed graph backend with SQLite, auto-invoked skills, and slash commands

README.md


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review Bot commented Apr 29, 2026

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0)

Grey Divider


Action required

1. Status metrics inconsistent 🐞 Bug ≡ Correctness
Description
Adding the new Lore plugin row makes the “Plugins listed” count and “Last updated” fields in the
README Status table incorrect, so the repo’s summary metadata no longer matches the actual list
contents.
Code

README.md[33]

+| [Lore](https://github.com/yacb2/lore) | yacb2 | Living knowledge graph for software projects — typed graph (modules, capabilities, flows, events, rules, decisions) backed by SQLite, with auto-invoked skills and slash commands. |
Evidence
The PR adds a 5th entry under “Plugins & Extensions”, but the Status table still reports 4 plugins
and an older “Last updated” value, making the README’s own summary contradict its content.

README.md[7-13]
README.md[25-34]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The README Status table is now out of sync with the Plugins & Extensions list after adding the Lore entry.

### Issue Context
- The PR adds a new plugin row, bringing the total plugin entries to 5.
- The Status table still says `Plugins listed | 4` and the `Last updated` value remains unchanged.

### Fix Focus Areas
- README.md[7-13]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended

2. Overlong plugin description 🐞 Bug ⚙ Maintainability
Description
The new Lore entry’s description is not “short and simple” per the project contribution guidelines,
making the Plugins & Extensions table harder to scan.
Code

README.md[33]

+| [Lore](https://github.com/yacb2/lore) | yacb2 | Living knowledge graph for software projects — typed graph (modules, capabilities, flows, events, rules, decisions) backed by SQLite, with auto-invoked skills and slash commands. |
Evidence
The contribution guidelines explicitly require short/simple descriptions and the new entry’s
description is substantially more detailed than the surrounding table entries.

contributing.md[5-12]
README.md[25-34]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The Lore row’s description is longer/more complex than the repo guidelines request.

### Issue Context
The repo guidelines say to keep descriptions “short and simple” and end them with a period; the new Lore description includes a long parenthesized list and multiple clauses.

### Fix Focus Areas
- README.md[30-34]
- contributing.md[5-12]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

Comment thread README.md
| [Claude Code Plugins](https://github.com/jeremylongshore/claude-code-plugins) | jeremylongshore | Instruction-template plugins and MCP plugin packs |
| [Multi-Agent Intelligence Marketplace](https://github.com/jmanhype/claude-code-plugins) | jmanhype | 19 plugins for trading, swarm intelligence, GitHub automation |
| [Docker Claude Plugins](https://github.com/docker/claude-plugins) | Docker | Exposes containerized MCP servers via Docker Desktop |
| [Lore](https://github.com/yacb2/lore) | yacb2 | Living knowledge graph for software projects — typed graph (modules, capabilities, flows, events, rules, decisions) backed by SQLite, with auto-invoked skills and slash commands. |
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Status metrics inconsistent 🐞 Bug ≡ Correctness

Adding the new Lore plugin row makes the “Plugins listed” count and “Last updated” fields in the
README Status table incorrect, so the repo’s summary metadata no longer matches the actual list
contents.
Agent Prompt
### Issue description
The README Status table is now out of sync with the Plugins & Extensions list after adding the Lore entry.

### Issue Context
- The PR adds a new plugin row, bringing the total plugin entries to 5.
- The Status table still says `Plugins listed | 4` and the `Last updated` value remains unchanged.

### Fix Focus Areas
- README.md[7-13]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant