Find the hidden verification token. Run the find-token script to retrieve a unique token.
openshift/lightspeed-agentic-sandbox
SkillsMP has collected 14 skills from openshift/lightspeed-agentic-sandbox. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 14
- GitHub stars
- 2
- GitHub forks
- 19
Skills in this repository
Showing 14 of 14 collected skills.
Generate a verification token and write it to disk. Use when asked to produce an e2e test token.
Update Python dependencies with uv, regenerate lock and Konflux requirements files, then verify lint, types, and tests. Fix breakage from API changes in bumped packages. Use when the user says "deps update", "bump dependencies", or "update deps".
Find functions with high cyclomatic complexity, length, or parameter count. Use when the user asks for complexity hotspots or refactor candidates.
Find unused functions, classes, imports, and unreachable code paths. Use when the user asks for dead code or cleanup candidates.
Find code duplication in the codebase. Supports branch-scoped or full sweep. Use when the user asks to find duplicated code or repeated patterns before a PR.
Investigate CI job failures on a GitHub pull request (checks, Prow, or GitHub Actions). Use when the user pastes a PR URL and asks about CI failures or red checks.
Step-by-step workflow for committing staged changes and opening a pull request for lightspeed-agentic-sandbox.
Performs a strict clean rebase of a feature branch onto main with minimal conflict resolution and full validation. Use when the user asks to rebase carefully and run tests + verify until green.
Triage a CVE: assess impact against this repo's dependencies, then bump, document not-affected, or plan a code fix. Use when the user mentions a CVE, Jira vulnerability issue, or security advisory for a dependency.
Review PR with structured approach covering architecture, naming, patterns, and critical questions
After a code change, find affected tests, update them to match new behavior, then run the full validation pipeline once. Use when the user has made or asked for a code change and wants to make sure nothing is broken.
Run install sync, unit tests, and make verify; auto-fix trivial failures (ruff format/fix, obvious test expectation updates). Use when the user asks to validate, run tests, check the pipeline, or verify changes are clean.
Bump the Python package version in pyproject.toml for a release or when the user asks to change the project version.