Skip to content

[AI] csb-dev skill#183

Draft
martin-beck wants to merge 1 commit into
open-s4c:mainfrom
martin-beck:martin/ai-skill-csb-dev
Draft

[AI] csb-dev skill#183
martin-beck wants to merge 1 commit into
open-s4c:mainfrom
martin-beck:martin/ai-skill-csb-dev

Conversation

@martin-beck

Copy link
Copy Markdown
Collaborator

No description provided.

Signed-off-by: Martin Beck <martin.beck2@gmx.de>
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@lilith218 lilith218 marked this pull request as draft June 29, 2026 11:20
Comment on lines +20 to +27
- `csb-remote` whenever reproduction or validation depends on an SSH benchmark
host, kernel, topology, container runtime, perf, bpftrace, sysstat, cgroups,
NICs, or host permissions.
- `csb-analysis` for interpreting existing result artifacts or preparing
evidence-backed kernel patch material.
- `csb-refine` for iterative benchmark reruns and kernel-performance
refinement loops.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Suggested change
- `csb-remote` whenever reproduction or validation depends on an SSH benchmark
host, kernel, topology, container runtime, perf, bpftrace, sysstat, cgroups,
NICs, or host permissions.
- `csb-analysis` for interpreting existing result artifacts or preparing
evidence-backed kernel patch material.
- `csb-refine` for iterative benchmark reruns and kernel-performance
refinement loops.

Not sure why these are relevant for development.


## Development Guardrails

- Keep edits scoped and follow existing runner, config, monitor, plugin,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

If this skill is about generating code (development), we should add somewhere that

all modifications should pass

  • helpers/python-checks.sh
  • new code should be well documented
  • prefer using existing functionality over duplicating code
  • follow the existing style and conventions
  • add unit tests whenever possible
  • run python-tests.sh and make sure all tests pass

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