automation-using-scriptcollection

Name: automation-using-scriptcollection
Availability: InStock
Author: anionDevelopment

Documents ScriptCollection commands for building, testing, and releasing common-project-structure repositories.

Updated Jun 13, 2026

Search Tags:#testing #release #build automation #taskfile #ci pipeline #codeunit #scriptcollection

Ready to run

npx skills add https://github.com/anionDevelopment/Epew --skill automation-using-scriptcollection-aniondevelopment

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: automation-using-scriptcollection
Source: https://github.com/anionDevelopment/Epew/tree/main/.agents/skills/automation-using-scriptcollection
Command: npx skills add https://github.com/anionDevelopment/Epew --skill automation-using-scriptcollection-aniondevelopment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories implementing the common project structure rely on dozens of ScriptCollection commands and conventions, and this Skill explains which commands exist, when to use them, and which files are generated automatically so you never edit the wrong file or guess command behavior. ## Core Features & Use Cases - Build Pipeline Guidance: Explains the codeunit scripts (Build.py, Linting.py, RunTestcases.py) and the scbuildcodeunits command with its switches for containerized builds, fastlane, and idempotency checks. - Command Reference: Covers sc-commands for quality checks, dependency updates, Docker networks, certificates, changelog entries, and releases. - Generated File Rules: Clarifies that Taskfile.yml, diagrams, and synchronized skill folders are derived from sources and must never be edited manually. - Use Case: When a visual-regression test fails after an intended UI change, use this Skill to learn that baselines must be regenerated with task UpdateVisualRegressionBaselines and committed together with the change. ## Quick Start Ask the AI to explain how to build all codeunits of this repository using ScriptCollection and which files will be regenerated automatically.

Frequently Asked Questions about automation-using-scriptcollection

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

FAQPage Schema

How do I build all codeunits in a common project structure repository?▼

Run scbuildcodeunits in the repository root to execute all codeunit scripts in dependency order. Use scbuildcodeunitsc for a containerized build, or the task aliases bb and bd defined in the generated Taskfile.yml.

How do I update visual regression test baselines?▼

Run task UpdateVisualRegressionBaselines to regenerate baseline screenshots inside a container. Only regenerate when the appearance change was intended, review the image diff, and commit the new baselines together with the causing change.

Can I edit Taskfile.yml manually to add a task?▼

No, Taskfile.yml is generated from the repository's .code-workspace file by scgeneratetaskfilefromworkspacefile. Change the tasks-section of the workspace file and regenerate, otherwise manual edits are lost on the next build.

How do I know if a repository uses ScriptCollection?▼

A repository uses ScriptCollection if a .ScriptCollection folder exists, codeunit scripts import from ScriptCollection.TFCPS, or Taskfile.yml contains tasks calling sc-commands. The common project structure alone does not imply ScriptCollection.

Why do my database testcases fail in the build pipeline?▼

Some testcases require local testservices such as MariaDB, PostgreSQL, or a reverse proxy to be running. Start them with the corresponding Localtestservice tasks before running the tests.

Where do I find the exact behavior of an sc command?▼

Read the source code in the ScriptCollection repository: Executables.py defines each command's arguments, TFCPS contains pipeline logic, and every command supports --help. Do not derive behavior from the command name.