create-ssdlc-mitigation-issue

name	create-ssdlc-mitigation-issue
description	Create a mitigation tracking GitHub issue and update the threat model table tracking link.

Create SSDLC Mitigation Issue

Workflow

1) Preconditions

• Be on the branch where you want to record tracking links.
• Ensure gh auth status is logged in.

2) Pick the mitigation control name (exact match)

Choose a Control value from: docs/threat-modeling/threat-model-risk-assessment.md → “Mitigation Candidates (To Be Confirmed/Implemented)”.

3) Create the issue and update the table

The script maintains a standard list of repos where mitigations may require changes (code, pipelines, or settings):

• reductstore
• reduct-rs
• reduct-cpp
• reduct-js
• reduct-go
• reduct-py
• reduct-cli
• web-console
• reductstore-pro
• reduct-grafana
• reduct-bridge

Run the helper script (omit --repos to use the standard list):

python3 .kilo/skills/create-ssdlc-mitigation-issue/scripts/create_ssdlc_mitigation_issue.py \
  --control "Enforce branch protections + required reviews"

If the control name contains backticks (e.g., Least-privilege `GITHUB_TOKEN` permissions), use single quotes:

python3 .kilo/skills/create-ssdlc-mitigation-issue/scripts/create_ssdlc_mitigation_issue.py \
  --control 'Least-privilege `GITHUB_TOKEN` permissions'

To override the repo list for a mitigation that only applies to specific repos:

python3 .kilo/skills/create-ssdlc-mitigation-issue/scripts/create_ssdlc_mitigation_issue.py \
  --control "Enforce branch protections + required reviews" \
  --repos reductstore reduct-rs

The script will:

• Look up the mitigation row (Priority, TM IDs, evidence notes).
• Create a GitHub issue in the current repo with:
  • TM(s) addressed
  • motivation/context
  • links to docs/guides/* and the threat model
  • a per-repo checklist for applying changes (code/pipeline/settings as needed)
• Update the mitigation row’s “Tracking (issue/PR)” cell from TODO to an issue link.

4) Review and commit (no push unless asked)

git diff
git add docs/threat-modeling/threat-model-risk-assessment.md
git commit -m "docs: track mitigation <short control name>"

Notes

• If the table row is already tracked (not TODO), re-run with --force.
• Use --dry-run to preview the issue body and table edit without creating anything.