Skip to content

feat(agents): rename rfc-bau-nsg-fw to rfc; add clone-derived both-scope, multi-PR, and fallback handling - #194

Merged
jinyeow merged 3 commits into
mainfrom
feat/rfc-both-scope-multi-pr
Aug 23, 2026
Merged

feat(agents): rename rfc-bau-nsg-fw to rfc; add clone-derived both-scope, multi-PR, and fallback handling#194
jinyeow merged 3 commits into
mainfrom
feat/rfc-both-scope-multi-pr

Conversation

@jinyeow

@jinyeow jinyeow commented Aug 23, 2026

Copy link
Copy Markdown
Owner

Renames the rfc-bau-nsg-fw skill to rfc and extends it to handle both-scope changes,
multiple linked PRs, and an any-scope fallback, all clone-derived at runtime, never
hardcoded field values.

What changed

  • Skill renamed ai-agents/skills/rfc-bau-nsg-fw/ to ai-agents/skills/rfc/, with
    args-routing (/rfc bau firewall/nsg and friends implemented; other forms remain
    explicit stop-stubs).
  • Both-scope (firewall and nsg) changes are classified and cloned from the most
    recent BAU Firewall and NSG Rules prior RFC, using the same exact-title-prefix
    discipline as the existing single-scope lookup.
  • Every PR linked to the parent work item gets its own ArtifactLink relation, and scope
    is the union of all linked PRs' changed paths (each PR's own project/repo is resolved
    separately, since firewall and NSG config can live in different repos).
  • When no exact-scope match exists, the skill falls back to the most recent BAU
    firewall/NSG RFC of any scope, flagged as an inferred fallback in the confirmation
    table rather than treated as an exact match.
  • When no linked PR is found, scope falls back to conversation context and the PR title
    convention, flagged as inferred rather than detected from a diff.
  • Existing safeguards carried forward unchanged: latest-PR-iteration resolution,
    exact-title clone validation, unique per-run temp-file cleanup, and post-write
    read-back validation.
  • Added an "Adding a new RFC subtype" onboarding checklist to the skill's own SKILL.md.
  • Updated the ADR and spec cross-references for the rename and the new capabilities.
  • Two follow-up commits from a Fable + Codex review pass: a broken PowerShell pipeline
    in the per-PR repo lookup, a missing confirmation/read-back reminder on the documented
    PATCH-existing-RFC workaround, and small wording clarity fixes.

No field value (SharePoint URLs, distribution lists, named individuals' contact info, or
static CAB picklist values) is written into the skill file anywhere. Every repeated
field still comes from cloning a real prior RFC at runtime.

Closes #129.

Verification

  • git diff --check clean on every commit.
  • Reviewed by a Fable subagent (correctness/conventions/tests) and Codex (full rubric,
    high effort); two above-floor findings and three low-severity findings fixed.
  • Not yet verified against a real both-scope RFC creation in Azure DevOps, which needs
    live tenant access this environment doesn't have. The untracked prototype this skill
    supersedes (~/.claude/skills/rfc/) has already been deleted.

…notes

- Deserialize az pr show JSON before Select-Object -ExpandProperty repository (step 2)
- Note the existing-RFC PATCH aside still requires step 7 go-ahead and step 9 read-back validation
@jinyeow
jinyeow marked this pull request as ready for review August 23, 2026 13:11
@jinyeow
jinyeow merged commit 11c7914 into main Aug 23, 2026
5 checks passed
@jinyeow
jinyeow deleted the feat/rfc-both-scope-multi-pr branch August 23, 2026 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat(agents): rename rfc-bau-nsg-fw to rfc; add clone-derived both-scope, multi-PR, and fallback handling

1 participant