Skip to content

feat: add granola-engineer Cursor plugin - #19

Draft
donny-devops wants to merge 1 commit into
mainfrom
donny-devops/granola-engineer-plugin-8a71
Draft

donny-devops wants to merge 1 commit into
mainfrom
donny-devops/granola-engineer-plugin-8a71

Conversation

@donny-devops

@donny-devops donny-devops commented Sep 14, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds a thin Cursor plugin at plugins/granola-engineer/ (agent, /granola-engineer command, skill, always-on meeting rule, Granola MCP). This is not a fork of the official Granola marketplace plugin.
  • Mirrors the same files under .cursor/ so clones load the agent without a Marketplace install. .cursor-plugin/marketplace.json lists the plugin for team marketplace import.
  • tests/test_plugin.py checks manifests, required files, and overlay drift.
  • Agent prompt is kit-specific: sqlite3, public CRUD, optional GitHub session OAuth, /ops catalog is not live Cloudflare Analytics.

Test plan

  • ruff check . and ruff format --check .
  • pytest -v (80 passed, including 6 plugin fixture tests)
  • Plugin JSON parses; overlay matches plugins/granola-engineer/
  • In Cursor: /granola-engineer is available; first Granola MCP call can sign in (needs a Granola account in the desktop app)
Open in Web Open in Cursor 

Ship a thin kit-specific plugin (agent, /granola-engineer command, skill,
always-on meeting rule, Granola MCP) under plugins/granola-engineer, mirror
it in .cursor/ so clones load it, and fail tests if the overlay drifts.

Co-authored-by: Adonis Jimenez <donny-devops@users.noreply.github.com>
@ecc-tools

ecc-tools Bot commented Sep 14, 2026

Copy link
Copy Markdown

ECC Tools / Security Evidence

Commit: 97d67a7f21e8c90a21edd34487a53e507bbf5732

Security scanner evidence required (action_required)

Detected 1 security-sensitive predictive risk signal(s) without scanner evidence.

Mode: enforce

Findings:

  • Security-sensitive changes may ship without scanner evidence: The PR touches billing, secrets, auth, webhooks, agent, or CI-sensitive surfaces without adding obvious security scanner, code scanning, or security-focused validation evidence. (2 security-sensitive paths changed; 0 security scanner or security-focused validation artifacts changed)

Touched security-sensitive paths:

  • .cursor/agents/granola-engineer.md
  • plugins/granola-engineer/agents/granola-engineer.md

Expected evidence:

  • Security scanner, code scanning, secret scanning, dependency/security review, or focused security regression output.
  • SARIF/code-scanning upload or equivalent pass/fail gate for the changed surface.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 14, 2026

Copy link
Copy Markdown

ECC Tools / PR Risk Taxonomy

Commit: 97d67a7f21e8c90a21edd34487a53e507bbf5732

PR taxonomy review recommended (neutral)

Detected 3 PR taxonomy bucket(s): Security Evidence, Install Manifest Integrity, CI/CD Recommendation.

Scanned 18 changed file(s).

Roadmap taxonomy buckets:

Security Evidence

Security-sensitive changes should carry explicit scanner, code-scanning, or focused regression evidence.

Signals:

  • Security-sensitive changes may ship without scanner evidence
  • 0 security-sensitive path(s) changed

Paths:

  • .cursor-plugin/marketplace.json
  • .cursor/agents/granola-engineer.md
  • .cursor/commands/granola-engineer.md

Install Manifest Integrity

Install manifests, plugin metadata, and shipped skills should stay synchronized with user-facing setup guidance.

Signals:

  • 2 install or manifest path(s) changed

Paths:

  • .cursor-plugin/marketplace.json
  • plugins/granola-engineer/.cursor-plugin/plugin.json

CI/CD Recommendation

CI, dependency, coverage, and contract signals should be routed into follow-up checks or verification work.

Signals:

  • CLI changes may ship without shell or end-to-end coverage
  • 0 CI or workflow path(s) changed

Paths:

  • .cursor-plugin/marketplace.json
  • .cursor/mcp.json
  • plugins/granola-engineer/.cursor-plugin/plugin.json
  • plugins/granola-engineer/mcp.json
  • tests/test_plugin.py

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 14, 2026

Copy link
Copy Markdown

ECC Tools / Reference Set Readiness

Commit: 97d67a7f21e8c90a21edd34487a53e507bbf5732

Reference set readiness gaps detected (neutral)

Reference evidence present for 1/7 areas (14%) across 18 changed file(s).

This check is based on files changed in this PR. Repository-level readiness is still reported by /ecc-tools analyze comments and generated manifests.

Area Status Evidence / Next Step
Deep analyzer corpus Missing Add analyzer fixture, golden, benchmark, or reference-set files that can catch analyzer regressions.
RAG/evaluator comparison Missing Add retrieval or evaluator reference-set comparison fixtures with expected ranking behavior.
PR salvage/review corpus Missing Add stale-PR, review-thread, reopen-flow, or salvage reference cases for queue cleanup automation.
Discussion triage corpus Missing Add public discussion triage fixtures, golden cases, or reference sets for informational, answered, and no-response classifications.
Harness compatibility Present tests/test_plugin.py
Security evidence Missing Attach security evidence such as SBOMs, SARIF, audit reports, or AgentShield evidence packs.
CI failure-mode evidence Missing Add captured CI failure logs, dry-run fixtures, or troubleshooting docs for common workflow failure modes.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@ecc-tools

ecc-tools Bot commented Sep 14, 2026

Copy link
Copy Markdown

ECC Tools / Hosted Promotion Readiness

Commit: 97d67a7f21e8c90a21edd34487a53e507bbf5732

Hosted promotion readiness passed (success)

No hosted promotion evidence gaps detected across 18 changed file(s); 0 corpus scenarios had matching evidence.

This check compares PR file changes against the evaluator/RAG promotion corpus in src/analyzers/fixtures/evaluator-rag-corpus.ts.
Hosted output scoring inspected 0 completed cached hosted job results.

No evaluator corpus scenarios matched this PR.

Check publication was denied or unavailable. An app owner must enable Checks: read and write, and the installation owner must approve the updated permission.

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Review Summary

This PR adds a Cursor plugin for Granola integration to anchor FastAPI development to meeting context. The implementation includes comprehensive test coverage and proper documentation.

Critical Issues (2)

  • PII exposure: Personal email address committed to marketplace.json - should use generic or organization email
  • Duplicate section header: "Commit messages" appears twice in CONTRIBUTING.md

Overall Assessment

The plugin structure is well-organized with proper mirroring between plugins/ and .cursor/ directories. Tests validate plugin manifests, required files, and overlay synchronization. Once the identified issues are addressed, this will be ready to merge.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

Comment thread CONTRIBUTING.md
Comment on lines +54 to +55
## Commit messages

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Remove duplicate section header "Commit messages". The section header appears on both line 54 and line 56.

"name": "fastapi-starter-kit-plugins",
"owner": {
"name": "donny-devops",
"email": "mr.adonisjimenez@gmail.com"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🛑 PII Exposure: Personal email address is publicly committed to version control. Replace with a generic or organization email address to avoid spam and privacy concerns.

Suggested change
"email": "mr.adonisjimenez@gmail.com"
"email": "plugins@donny-devops.example.com"

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.

2 participants