epam/cloud-pipeline

dev-sandbox

Create, check, connect to, extend or remove a throw-away AWS sandbox for live testing (a Kubernetes 1.15 master on EC2, tagged to one developer, driven by scripts/sandbox.sh, and reached from local containers through a tunnel), run the platform's API, its…

verify-client-live

Open a user-visible client/ change in a browser against a real Cloud Pipeline deployment, or a dev sandbox. Use when the diff changes UI layout, routing, client state or rendered data — not for tests, the test/ harness, lint/build config, or non-visual edits.…

verify-changes

Find and run the checks a change owes, from what it touches and what that can reach. Use after editing any file, when about to call a change finished, or when asked whether something passes.

commit-changes

Required before you commit, push or open a pull request here, asked or not. Holds the preconditions, the subject line and its trailers, the draft PR, and the issue label afterward.

file-issue

Create a new GitHub issue in this repository — a bug report, an enhancement request, or a followup/sub-issue found while implementing another task. Use when asked to file, open, or write up an issue, not when implementing one that already exists.

implement-task

Start here before the first edit of any file — a one-liner and a docs change included. Holds the steps a task passes through, the issue number and branch it needs, the tests and docs it owes, and where the branch ends up. The plan-change, verify-changes and…

modifying-instructions

Required before adding or changing anything an agent reads — a convention in AGENTS.md, a procedure as a skill, a pattern-scoped rule. Holds which of those a thing belongs in, the wiring each needs before it loads at all, and what to keep out of them.

configure-dev-environment

Learn which toolchains and environments this workstation has and how to invoke them, or set them up when they are missing. Load this before building, testing or running anything in this repository.

plan-change

Plan the work before you edit — its phases, the model and effort each takes, and whether it is worth a plan file with a ledger beside it. Also when resuming a plan, or told to continue one.