ic3-development-guide

Guides IC3 software development workflows including SWC creation, integration builds, and baseline tagging.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/deriye/.agents-work --skill ic3-development-guide-deriye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ic3-development-guide
Source: https://github.com/deriye/.agents-work/tree/main/skills/ic3-development-guide
Command: npx skills add https://github.com/deriye/.agents-work --skill ic3-development-guide-deriye

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? IC3 software development involves complex multi-repository workflows across app_ic, vap_template, and ECU_IC3, with frequent build failures caused by missing MSW tags, unmapped signals, and SEWS container misconfigurations. This Skill consolidates the commands, workflows, and troubleshooting steps needed to create, update, and rename Software Components without hunting through scattered Confluence pages. ## Core Features & Use Cases - SWC Lifecycle Management: Step-by-step workflows for creating new SWCs, updating signal configurations, and renaming existing components including SEWS2 container handling. - Integration & Build Commands: Complete reference for make targets (gen_dvcfg, win_build, v3_load_package), Gradle unit tests, and PAQR test generation. - Error Troubleshooting: Maps common build errors like missing MSW tags and S-record failures to concrete fixes. - Use Case: When a developer needs to rename an SWC, the Skill walks through vap_template updates, SEWS2 container creation, code porting, unit test execution, and integration build verification in the correct order. ## Quick Start Ask the assistant to walk you through creating a new SWC for IC3, including the vap_template configuration, SEWS container setup, and generation commands.

Frequently Asked Questions about ic3-development-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new SWC in IC3 development?▼

Create feature branches in app_ic and vap_template, configure the SWC Python files in vap_template components, create a SEWS2 container, then run make create_app_ic_xml and create_IC_solution.sh to generate the SWC structure. Finally configure swc_info.json with requirements and parameters.

How do I fix the TypeError cannot use a string pattern on a bytes-like object build error?▼

This error means a build tag is missing on your branch. Create an MSW tag with git tag MSW_[partno]_3.[baseline].0, push it to the remote, and run git fetch --tags --force to synchronize tags locally.

How do I run unit tests for a single SWC with Gradle?▼

Run ./gradlew :SWC_NAME:test to execute unit tests for one SWC, or ./gradlew :SWC_NAME:coverage to include a coverage report. Use ./gradlew :test to run tests across all SWCs in the repository.

What is the process for renaming an existing SWC?▼

Rename the Python files in vap_template, create a new SEWS2 container matching the new name exactly, regenerate the SWC structure, manually port source files and swc_info.json entries, run unit tests, then delete the old SWC directory only after tests pass.

Why does the integration build fail with First character not S in S-record?▼

This error means the DWM hex file was not uploaded to Artifactory with the new part number. Fix it by running make all and make release inside the ecu_ic3/dwm_config directory.

How do I export a SEWS container for use in vap_template?▼

In SEWS2, open the container, select Export SWC with DCM version Asr4Dcm2, download and unzip the file into the sews2template directory, then run sews2template.py to generate the SEWS Python template for the parameters folder.