Skip to content

Add keelson to Plugins & Extensions#52

Open
dhopkalo wants to merge 2 commits into
jmanhype:mainfrom
dhopkalo:add-keelson
Open

Add keelson to Plugins & Extensions#52
dhopkalo wants to merge 2 commits into
jmanhype:mainfrom
dhopkalo:add-keelson

Conversation

@dhopkalo

@dhopkalo dhopkalo commented Jun 7, 2026

Copy link
Copy Markdown

Adds keelson (MIT, maintainer: InnoVestrum) to Plugins & Extensions.

keelson establishes a tracker-agnostic, issue-driven agentic operating model in any repo: agents run mechanical work autonomously and escalate any move touching the original design, plan, or strategy to a human. Ships two Agent Skills (adopt-keelson, tune-gates).

Single-row addition; description ends with a period per the contribution guidelines.

@qodo-code-review

Copy link
Copy Markdown

Review Summary by Qodo

Add keelson to Plugins & Extensions

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Adds keelson plugin to Plugins & Extensions list
• Keelson enables tracker-agnostic agentic operating model
• Agents autonomously handle mechanical work with human escalation
Diagram
flowchart LR
  README["README.md<br/>Plugins List"]
  keelson["keelson Plugin<br/>InnoVestrum"]
  README -- "adds entry" --> keelson

Loading

Grey Divider

File Changes

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

Add keelson plugin table entry

• Adds single row entry for keelson plugin to Plugins & Extensions table
• Includes link to keelson GitHub repository
• Provides description of keelson's tracker-agnostic agentic operating model capabilities
• Maintains consistent formatting with existing table entries

README.md


Grey Divider

Qodo Logo

@qodo-code-review

qodo-code-review Bot commented Jun 7, 2026

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0)

Grey Divider


Remediation recommended

1. Plugins listed count incorrect ✓ Resolved 📘 Rule violation ≡ Correctness
Description
A new plugin row (keelson) was added, but the README Status table still reports `Plugins listed
| 4 (and retains an older Last updated` value), making the document internally inconsistent and
misleading. This breaks the existing documentation pattern within the modified section.
Code

README.md[33]

+| [keelson](https://github.com/innovestrum/keelson) | InnoVestrum | Tracker-agnostic, issue-driven agentic operating model; agents run mechanical work and escalate strategic decisions to a human. |
Evidence
The citations point to the README’s ## Status table where it tracks metrics like the total number
of plugins (and a Last updated timestamp), while the Plugins & Extensions table below now
contains five plugin rows including the newly added keelson entry; because the list grew by one,
the Plugins listed count (and potentially the Last updated field) should be updated to match the
current contents and maintain the README’s established conventions.

CLAUDE.md: Code Changes Must Follow Existing Code Style and Patterns: CLAUDE.md: Code Changes Must Follow Existing Code Style and Patterns
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 outdated: after adding the `keelson` entry to the **Plugins & Extensions** table, the `Plugins listed` count still shows `4` (and the `Last updated` value may also be stale), making the README internally inconsistent.
## Issue Context
The plugins table now contains 5 entries including `keelson`, but the Status section still claims 4 plugins and references an older last-updated period/value.
## Fix Focus Areas
- README.md[7-13]
- README.md[25-34]

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


Grey Divider

Qodo Logo

@dhopkalo

dhopkalo commented Jun 7, 2026

Copy link
Copy Markdown
Author

Thanks @qodo-code-review — good catch. Updated the Status table to keep it consistent: Plugins listed 4 → 5 and Last updated → 2026-Q2.

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