Skip to content

chore: sync skills from sg-clickhouse-mcp #25

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
arunim2405 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: sync skills from sg-clickhouse-mcp #25

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion skills/sg-create-workflow/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -295,7 +295,16 @@ parameter entirely otherwise (its defaults still apply omitted):
- `githubComSync`: advanced GitHub PR-trigger behavior, e.g.
`{"pull_request_opened": {"createWfRun": {"enabled": true}}}`. Free-form and
NOT validated by the platform, so a wrong key fails silently — most
workflows omit it entirely.
workflows omit it entirely. For push/PR/tag triggers use `vcsTriggers`.
- `vcsTriggers`: git events that start runs, e.g. `{"onPush": true,
"pullRequests": "trackedBranch", "trackedBranch": "main",
"approvalPreApply": true}`. **Git source only**, and the repo must be private
with `gitAuthRef` set (on GitLab, Bitbucket and Azure DevOps, a VCS
connector rather than a stored token). PR runs only plan; push and tag runs
apply unless `planOnly` or `approvalPreApply` is set. `fileFilters` (fnmatch
globs such as `["stacks/vpc/*"]`) limits runs to matching changes. The triggers are
registered right after the create; if that fails, the workflow still exists
and the response's `warnings` says how to retry.

Confirm a plain-language summary of everything collected with the user, then
call `create_workflow` with all parameters.
Expand Down
9 changes: 8 additions & 1 deletion skills/sg-update-workflow/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -195,7 +195,14 @@ Ask the user what they want to change, then build ONLY those parameters:
template upgrade.
- **GitHub PR triggers** (`githubComSync`) — REPLACES wholesale. Free-form and
not validated by the platform, so confirm the exact shape with the user
rather than guessing keys.
rather than guessing keys. For push/PR/tag triggers use `vcsTriggers`.
- **Git triggers** (`vcsTriggers`) — MERGES over the stored triggers, so pass
only what changes (`{"planOnly": true}`); turn one off with `false` or
`"pullRequests": "off"` (which also turns off the PR switches in a stored
`githubComSync`). Git source only (private repo with `gitAuthRef`),
and not together with a template upgrade. Sent after any other change in
the same call: if it fails, the other changes stay applied and `warnings`
says so.

## Step C — Confirm and update

Expand Down
2 changes: 1 addition & 1 deletion skills/sg-writing-stackguardian-workflow-terraform/references/execution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ workflow-step-templates source.
| `run_pre_init/pre_plan/post_plan_hooks_on_drift` | run those hooks during drift runs too (default false) |
| `wf_step_template_revision_id` | `workflow_from_template` only — custom runtime image |

Not settable: `tfvarsFilePath`, `terraformApplyOptions`. For a tfvars file in the repo use
Not settable: `terraformApplyOptions`. For a tfvars file in the repo use
`terraform_plan_options = "-var-file=env/prod.tfvars"` (only plan takes var files).
`terraform_config` is replaced **whole** on every update, which the provider handles by always
sending the full object.
Expand Down
Loading