Feat/onboarding_agent using bazel - #177
aryansingh0012 wants to merge 11 commits into
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
|
Documentation preview for this pull request is available at: |
| ## Onboarding | ||
|
|
||
| The repository includes the `score_onboarding` Bazel module to guide | ||
| contributors into the appropriate Eclipse S-CORE SDLC workflow. From the |
There was a problem hiding this comment.
What is the meaning of SDLC ? Software Development Life Cycle ?
| The onboarding agent (`tools/onboarding/`): | ||
| - identifies repository context (ASIL, languages, toolchains, build/docs system) | ||
| - classifies your contribution (bug fix, improvement, PoC, documentation, feature, question) | ||
| - recommends a workflow (SDLC Harness, SpecKit, BMAD, Technical Analysis, Issue Planning, Traditional) |
There was a problem hiding this comment.
What is BMAD ? Breakthrough Method for Agile AI-Driven Development ?
Signed-off-by: aryansingh0012 <aryan.s@ltts.com>
Signed-off-by: aryansingh0012 <aryan.s@ltts.com>
| it does not execute SDLC Harness, Technical Analysis, or Planning itself. | ||
|
|
||
| ## Role Detection | ||
| Ask the contributor for their role: `developer`, `reviewer`, `maintainer`, or |
There was a problem hiding this comment.
Where comes these roles from? S-CORE roles are defined here https://eclipse-score.github.io/process_description/main/roles/index.html#project-roles-list
| - `qnx` (in `MODULE.bazel` or `scripts/`) → QNX | ||
|
|
||
| ## Contribution Classification | ||
| Ask for the contribution type: `bug_fix`, `improvement`, `poc`, |
There was a problem hiding this comment.
This is not S-CORE definition, we have Feature Requests, Component Requests, etc., check for contribution guidelines
| - `documentation` → Traditional | ||
| - otherwise → Technical Analysis / Issue Planning | ||
|
|
||
| If the repository's ASIL level is not `QM`, always recommend SDLC Harness |
There was a problem hiding this comment.
Qm also must fulfill traceability, please follow S-CORE process_description and do not invent a new workflow
|
|
||
| # Onboarding Skill | ||
|
|
||
| Single entry point into the Eclipse S-CORE AI SDLC ecosystem. Collects |
There was a problem hiding this comment.
S-CORE AI SLDC does not exist, must be defined and shall be follow S-CORE process_description
| ## Repository Discovery | ||
| Read (never execute) `MODULE.bazel`, `project_config.bzl`, `README.md`, and | ||
| `CONTRIBUTION.md` at the repository root. Extract: repository name, module, | ||
| ASIL level, declared languages, build system. |
There was a problem hiding this comment.
ASIL Level is declared in the sphinx model
The repository includes the score onboarding Bazel module to guide
contributors into the appropriate Eclipse S-CORE SDLC workflow. From the
repository root, start the interactive flow.