القائمة
Use when adding or updating CI/CD integrations in the raps-actions repo — GitHub Actions composite actions, GitLab CI include templates, test workflows, and floating tag management.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when adding a new MCP tool to the RAPS MCP server — covers tool schema definition, handler implementation, dispatch registration, and the client accessor pattern.
Use when adding a new CLI command or subcommand to RAPS — covers the clap struct pattern, module wiring, output formatting, and test structure across the 10-crate workspace.
Use when new RAPS features ship and LinkedIn content is needed — adds posts to the raps-smm post bank following established tone, format, and hashtag conventions.
Use when bumping the RAPS version for a new release — updates Cargo.toml workspace version, 9 internal crate dependencies, 6 npm package.json files, creates git tag, and triggers the release workflow.
Use before releases or after dependency updates to run security checks — cargo-audit, ASVS compliance matrix review, clippy security lints, redaction pattern verification.
Use when you need to create a shortened URL at go.rapscli.xyz — for long Cloudflare OAuth links, wrangler login URLs, or any URL that's unwieldy in the terminal.
| name | raps-ci-cd-templates |
| version | 1.0 |
| description | Use when adding or updating CI/CD integrations in the raps-actions repo — GitHub Actions composite actions, GitLab CI include templates, test workflows, and floating tag management. |
Manage GitHub Actions and GitLab CI templates in the raps-actions repo.
Repo: /root/github/raps/raps-actions
raps-actions/
├── setup/action.yml # GitHub Action: install + auth
├── pipeline/action.yml # GitHub Action: run pipeline
├── upload/action.yml # GitHub Action: upload to OSS
├── translate/action.yml # GitHub Action: translate model
├── gitlab/
│ ├── setup.yml # GitLab: .raps-setup hidden job
│ ├── pipeline.yml # GitLab: .raps-pipeline
│ ├── upload.yml # GitLab: .raps-upload
│ ├── translate.yml # GitLab: .raps-translate
│ └── example.gitlab-ci.yml # GitLab: complete example
├── .github/workflows/
│ └── test.yml # Tests setup + pipeline dry-run
└── README.md
name: "RAPS Action Name"
description: "What it does"
branding:
icon: "terminal"
color: "orange"
inputs:
param:
description: "Description"
required: true
default: "value"
outputs:
result:
description: "Description"
value: ${{ steps.step-id.outputs.result }}
runs:
using: "composite"
steps:
- name: Step name
shell: bash
env:
VAR: ${{ inputs.param }}
run: |
# Logic here
echo "result=value" >> "$GITHUB_OUTPUT"
Key: All actions use shell: bash. Setup action installs via install.sh (not npm).
.raps-action-name:
extends: .raps-setup
script:
- raps command here
- |
if [ "${RAPS_OPTION:-default}" = "value" ]; then
raps another-command
fi
Key: Hidden jobs (.raps-*) with extends: .raps-setup. Variables via CI/CD settings, not with: inputs.
After pushing changes, update the floating tag so users on @v1 get the latest:
git tag -f v1
git push origin v1 --force
GitHub Actions users reference @v1. GitLab users reference the raw URL with v1 in the path.
# Trigger test workflow manually
gh workflow run test.yml
# Watch results
gh run list --workflow=test.yml --limit 1
gh run view <run-id>
Test workflow validates: setup action installs RAPS, pipeline dry-run succeeds.
<name>/action.yml following the composite patterngitlab/<name>.yml with matching hidden jobgitlab/example.gitlab-ci.ymlREADME.md with both GitHub and GitLab docs.github/workflows/test.yml to cover new actionnpm install instead of install.sh for setup (npm platform binaries may lag)shell: bash on composite action stepsjq in actions (not available by default — use grep/cut instead)