No description
- feed/cieng_feed.ps1: -Seconds (default, LEVEL +/-25 %), -UntilFlag (DEMO.FEED_ON for the display Start/Stop), -Alarms (+/-33 %, crosses L/H), -System (SYSTEM.* items, skipped while the monitoring processes run); single-copy lock; log in %TLS_LST_PATH%\cieng_feed.log - feed/cieng_feed_start.cmd, feed/install_feed.ps1: installed to C:\Users\Public\CI-Eng-Sample\feed (outside the CI Server package) for the server-side display command - Item CI-Eng-Sample.DEMO.FEED_ON in 02_item_df.qli / 91_remove_item_df.qli - Tested on CI Server R1.03.00 2026-10-06: default run, single copy, start wrapper with flag stop, system items written and skipped with a monitor process present Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .claude/skills | ||
| examples | ||
| knowledge | ||
| tools | ||
| CLAUDE.md | ||
| README.md | ||
ci-server-config
A knowledge base that lets Claude Code work as a Yokogawa CI Server (R1.03) engineer. Open this repo in Claude Code and describe what you want to do in CI Server.
Layout
| Path | Contents |
|---|---|
CLAUDE.md |
Always-loaded instructions: role, version, where to look |
.claude/skills/ |
How to do things. One skill per CI Server area; each task is its own file |
knowledge/ |
Shared reference. Document map, glossary, known issues, cross-area concepts |
examples/ |
Verified, working artifacts (class descriptions, reports, scripts) |
tools/ |
Helper scripts Claude can run (e.g. the setup check) |
Prerequisites
Using the repo needs no manuals: the knowledge is in knowledge/ and .claude/skills/.
Only to extend the repo (summarize a manual, check a citation) you need the CI Server EN
manuals locally. They are not stored in this repo. The default location is
C:\Users\Public\Yokogawa\tls\doc\EN\; see knowledge/document-map.md if yours is different.
Contributing
- Add task knowledge under the matching skill:
.claude/skills/<area>/tasks/<task>.md, and add a row to that skill'sSKILL.mdindex. - Write in your own words, cite the manual (IM number + section) and the version, and mark the content as verified or from docs.