// Assign @copilot on an existing SecOps remediation issue after policy guard—use when Project link or org policy requires Issue → Project before assignee. Uses gh issue edit; does not push branch code.
| name | secops-assign-copilot-to-issue |
| description | Assign @copilot on an existing SecOps remediation issue after policy guard—use when Project link or org policy requires Issue → Project before assignee. Uses gh issue edit; does not push branch code. |
Workflow: Submit phase — run scripts/assign-copilot-issue.sh after policy guard. Same script for humans and Claude; see docs/product_design.md.
@copilot on an existing issue number without recreating the body.Assignment semantics and GHES limits: ../secops-create-remediation-issue/references/gh-issue-copilot.md.
owner/repo, issue number.scripts/assign-copilot-issue.sh — validate-repo, then gh issue edit … --add-assignee "@copilot". Args: --repo OWNER/REPO --issue NUMBER.
.claude/skills/secops-assign-copilot-to-issue/scripts/assign-copilot-issue.sh \
--repo OWNER/REPO --issue 42
Prerequisites: pnpm --filter @github-secops-agent/ghclt build, gh. Optional SECOPS_CONFIG. Next: secops-check-pr-checks when a PR exists; secops-project-board-sync as needed for board fields.
git push to the target repository.--body-file.--body-file when opening an issue; this skill only adds @copilot when assign was deferred (e.g. after Project link).Run pnpm build from the repo root and fix compile or build errors until the workspace build passes. Use after edits, when CI is red on build, or before opening a PR. Keywords: pnpm, build, TypeScript, monorepo, workspace.
Run pnpm format then pnpm lint from the repo root and fix issues until both pass. Use after edits, when CI is red on lint/format, or before opening a PR. Keywords: pnpm, format, lint, trunk, monorepo, code style.
Manage Architecture Decision Records (ADRs). Use this to initialize, create, list, and link ADRs to document architectural evolution. Requires 'adr-tools' to be installed.
Run pnpm test from the repo root and fix failing tests or implementation until the suite passes. Use after edits, when CI is red on tests, or before opening a PR. Keywords: pnpm, test, vitest, unit tests, monorepo.
Use at the end of a coding session to summarize outcomes, failures, inefficiencies, and root causes, then output a concise postmortem report with ranked improvements for next time. Output only in chat; do not edit project files unless the user explicitly asks. Skip nit-picks and one-off mistakes.
One-shot PR status check with gh—structured JSON outcome and exit codes; classify green vs failing vs pending vs blocked. Read-only on the repo. Does not loop; re-invoke on a schedule (human, Claude, or optional sub-agent). No issue comments—use secops-post-ci-nudge-comment to nudge.