agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/sre-agent/labs/zava-learning/sre-config/agent-config/skills/pr-delivery/SKILL.md

pr-delivery

Skill187 starsChanged 6 months agoMITView on GitHub

Use to deliver a durable Zava Learning fix as a GitHub pull request once an incident has been root-caused — for either an Infrastructure-as-Code change (Bicep under infra/) or an application code change (under src/). The single skill that creates pull requests; applies after live mitigation and root-cause confirmation. The resulting PR URL is what the ServiceNow Change Request references.

  • Reads credentials

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Commit with a conventional message: fix(<area>): <symptom> — <root cause> and a body that summarizes the RCA and links the PagerDuty …

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Zava Learning — Pull Request Delivery (IaC + Code)

Single owner of GitHub pull-request creation for durable fixes. Repo: @@REPO@@ (hosts the app src/ and the infrastructure infra/). This skill applies once an incident is root-caused and the live mitigation is in place; the pull request it produces is later referenced by the ServiceNow Change Request (servicenow-change-management).

There is no native GitHub pull-request tool — author the branch, commit, and open the PR with ExecutePythonCode (GitHub REST API / gh) using FindConnectedGitHubRepo and GetIaCForGitHub to locate the repo and IaC. Never commit secrets. Before opening the PR, retrieve SearchMemory("zava-redaction") and run its redact() over the PR title, body, and commit message (and never stage a credential or .env/*.pem/git-credentials file into the diff).

When to use

  • An incident is root-caused to a durable defect and the live mitigation is already applied.
  • The fix belongs in version control: IaC (infra/, e.g. an NSG rule in infra/modules/network.bicep, or a value in infra/main.parameters.json) or application code (src/, e.g. a synchronous crypto regression in src/assessment-api/server.js).

Decide the change class

  • Infrastructure (IaC): the fix is a guardrail or config in Bicep / parameters. Make BOTH live Azure and the committed IaC reflect the corrected state so the next deploy keeps the fix.
  • Application code: the fix is in src/. The live mitigation was a revision rollback/restart; the PR carries the actual code correction.

Steps

  1. Resolve the repo and IaC type (FindConnectedGitHubRepo, GetIaCForGitHub).
  2. Branch from default: fix/<symptom-slug> (e.g. fix/quiz-launch-nsg-priority).
  3. Apply the minimal, surgical change. Match existing style. Touch only what the root cause requires.
  4. Commit with a conventional message: fix(<area>): <symptom> — <root cause> and a body that summarizes the RCA and links the PagerDuty incident.
  5. Open the PR against @@REPO@@. PR body must include: symptom, root cause, the change, verification evidence (link the Before/After), and the PagerDuty incident number.
  6. Capture the PR URL — the ServiceNow Change Request (servicenow-change-management) references it. Post the PR link back in the PagerDuty incident notes.

Out of scope (human approval required)

  • Merging the PR, force-pushes, history rewrites, changes outside the root-cause fix, VNet/subnet/IAM changes.

Verification

The PR is open against the correct repo/branch with a complete RCA-backed description and a linked Change Request; CI (if any) is green. Report the PR URL.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free