Merge pull request #4 from maggiezha/k8s-autoscaling

K8s autoscaling

Author: maggiezha

.agents/catalog-skills.yaml

@@ -0,0 +1,23 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# Stop for Git and GitHub Access Errors
+
+Use this rule in each workflow that runs `git`, `ssh`, or `gh` commands.
+
+Stop if a Git or GitHub command has an access error. Access errors include authentication, authorization, credentials, SSO, token scope, SSH keys, remote access, and push permissions.
+Ask the user to correct the access problem.
+
+Do not try to bypass an access error. Do not:
+
+- switch remote protocols or remotes
+- edit credentials, tokens, or SSH config
+- generate new tokens or SSH keys
+- rewrite remotes to bypass permissions
+- force-push or bypass branch protections or required checks.
+
+Report the command and the error. Tell the user which action is necessary. Then, wait.
+
+This rule applies only to access errors.
+Handle merge conflicts, stale branches, dirty worktrees, and rebase conflicts in the related workflow.
+Ask the user when a resolution can change behavior, contributor intent, or a design decision.

.agents/skills/_shared/git-github-hard-stop.md

@@ -0,0 +1,54 @@
+<!-- SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved. -->
+<!-- SPDX-License-Identifier: Apache-2.0 -->
+
+# Follow Up on PR CI and Reviews
+
+Use this workflow after you create a PR or push to an open PR.
+
+## Monitor checks
+
+```bash
+PR_NUMBER=${PR_NUMBER:-$(gh pr view --json number -q .number)}
+gh pr checks "$PR_NUMBER" --watch
+```
+
+When the checks stop, inspect their status:
+
+```bash
+gh pr view "$PR_NUMBER" --json url,statusCheckRollup,comments,reviews,reviewDecision
+```
+
+## Review feedback
+
+Check PR comments and inline review comments from CodeRabbit and the PR Review Advisor:
+
+```bash
+gh api "repos/NVIDIA/NemoClaw/issues/${PR_NUMBER}/comments" --paginate \
+  --jq '.[] | select((.body // "") | test("CodeRabbit|coderabbit|PR Review Advisor|nemoclaw-pr-review-advisor"; "i")) | {author: .user.login, updated_at, body}'
+
+gh api "repos/NVIDIA/NemoClaw/pulls/${PR_NUMBER}/comments" --paginate \
+  --jq '.[] | select((.body // "") | test("CodeRabbit|coderabbit|PR Review Advisor|nemoclaw-pr-review-advisor"; "i")) | {author: .user.login, path, line, updated_at, body}'
+```
+
+## Handle results
+
+- Follow the [NemoClaw Writing Guide](../../../WRITING.md) for review comments and proposed rewrites.
+- The guide defines which language findings can block and how to write a suggestion.
+- Before you act on feedback, state the problem and the intended result.
+- Do not add a helper, configuration switch, fallback, migration, or compatibility path only to satisfy reviewer wording.
+- Treat feedback as a suggestion if you cannot connect it to one of these conditions:
+  - A defect.
+  - A demonstrated security or data-safety risk.
+  - A supported contract.
+  - Unnecessary complexity in changed code.
+  - Ambiguity in changed text that can change behavior, security, data safety, test meaning, or release meaning.
+- **CI failure:** Inspect the job logs and fix the cause. Run the related local checks. Commit, push, and monitor the PR again.
+- **Valid CodeRabbit or PR Review Advisor finding:** Fix correctness, security, or test-coverage problems. Run the related checks. Commit, push, and monitor the PR again.
+- **Style comment or false positive:** Avoid unnecessary changes. Explain your decision in the final report. Comment on the PR when reviewers need the explanation.
+- **Ambiguous, risky, broad, or design-changing feedback:** Stop and ask the user before you change code.
+
+Repeat this workflow until required CI passes and no actionable automated-review findings remain. Stop if the user tells you to stop.
+
+If a push or GitHub query has an access error, follow [Git and GitHub Access Hard Stop](git-github-hard-stop.md).
+Resolve merge conflicts and dirty-worktree problems in the PR workflow.
+Ask the user when a resolution can change behavior or contributor intent.