Skip to content

chore(ai): add agent notes, Cursor rules, and skills - #2133

Draft
felipebergamin wants to merge 1 commit into
kernelci:mainfrom
profusion:chore/ai-initial-harness
Draft

felipebergamin wants to merge 1 commit into
kernelci:mainfrom
profusion:chore/ai-initial-harness

Conversation

@felipebergamin

Copy link
Copy Markdown
Member

Summary

  • Add AGENTS.md with where-to-look, commands, when/how to run the app, Postgres caveats, and project invariants for coding agents.
  • Add Cursor rules (frontend/backend/filters, collaboration, ponytail) plus vendored .agents skills and skills-lock.json.

Human onboarding stays in docs/Onboarding.md / CONTRIBUTING.md; this is the short agent-facing map.

Test plan

  • Open AGENTS.md and confirm commands/URLs match docs/dev-environment.md (make dev, ports 9000/5173/8000).
  • Confirm .cursor/rules/ and .agents/skills/ load in Cursor for this repo.
  • Confirm .pnpm-store/ is not in the PR.

Give coding agents a local map of commands, invariants, and review
skills so they follow project conventions without copying onboarding.

Signed-off-by: Felipe Bergamin <felipebergamin@profusion.mobi>
@felipebergamin
felipebergamin marked this pull request as draft September 22, 2026 20:29
@felipebergamin

Copy link
Copy Markdown
Member Author

@alanpeixinho please feel free to suggest your own rules and skills that you find relevant

@alanpeixinho

Copy link
Copy Markdown
Contributor

#1719 also brings some skills on it, might be worth it reviewing.

@@ -0,0 +1,40 @@
#!/usr/bin/env bash

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

what exatcly is this sript?

Comment thread AGENTS.md

## Git

Conventional Commits with a scope, e.g. `fix(tree-compare): restore drawer navigation`. One concern per commit/PR. PR titles match; describe why, how, trade-offs, tests; link issues; screenshots/GIFs for UI. CI green before asking for review. Commit with "Signed-off-by".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

we could include reminder to a github closes tags

4. Pass each subagent the same scoped diff/file context and ask it to return prioritized findings with file references and evidence.
5. After both finish, synthesize the results with findings first, deduplicated across reviewers. Weight overlapping findings more heavily, resolve disagreements with your own judgment, and keep summaries brief.

If individual background summaries are already visible to the user, do not restate them wholesale. Surface the unified verdict, the highest-signal findings, and any remaining uncertainty.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

maybe worth including a guard to ask for human intervention for review after it finishes running pre-review

Comment thread .cursor/rules/filters.mdc
@@ -0,0 +1,16 @@
---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

might be worth keeping a kci-dashboard folder, so we can know which skills are specific written for the project

@@ -0,0 +1,68 @@
---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is it worth keeping a non development related skill?

@alanpeixinho alanpeixinho left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Left some comments, none are blockers

This branch has not been deployed

No deployments
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