agentleFS
itentialitential/infra-agent-skills/skills/change-management/SKILL.md

change-management

Skill1 starsChanged 32 days agoApache-2.0View on GitHub

Create, update, and manage the approval/close lifecycle of a change request on a supported ITSM platform — currently ServiceNow (sn_chg_rest, full gate-check/approve/reject/close), Freshservice (API v2 — cancel-only, no API-level approve/reject or gate-check), Jira Service Management (customer request on a change-configured request type; discoverable transitions, no readiness gate; assignee-only one-shot approve/decline), and BMC Helix ITSM (simplified REST API — search/retrieve/update, no documented way to discover transitions or gates). Use when an agent needs to run any part of an ITSM change request lifecycle. Assumes an authenticated client/tool for the target platform's change management API is already available; this skill does not provision or authenticate it. Does not cover delete, CI association, conflict-checking, scheduling, or change-task endpoints. Not every platform supports every action — check references/INDEX.md before assuming approve/reject or gate-check are available.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use andreessen, business-investment-advisor and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Hussain-ElfalahSkill

    andreessen

    Also in 4 projects that use this

  • Hussain-ElfalahSkill

    business-investment-advisor

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    karpathy-coder

    Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.

    Also in 4 projects that use this

  • csiddhant796-blipSkill

    self-eval

    Honestly evaluate AI work quality using a two-axis scoring system. Use after completing a task, code review, or work session to get an unbiased assessment. Detects score inflation, forces devil's advocate reasoning, and persists scores across sessions.

    Also in 4 projects that use this

  • +8 more from Hussain-Elfalah

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 12 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Not for delete, CI association, conflict-checking, scheduling, or change-task endpoints — no platform procedure under this skill covers …

    line 17
  2. Distinctive:

    Does not cover delete, CI association, conflict-checking, scheduling, or change-task endpoints on any platform.

    line 69

“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “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

Change Management

Runs an ITSM change request lifecycle — create, update, approve/reject, gate-check, close — on whichever platform the caller is targeting, following that platform's own documented procedure and state model.

When to use this skill

  • Creating, updating, closing, or managing the approval workflow of a change request on a supported ITSM platform — exactly which of those (including approve/reject and gate-check) the target platform supports is platform-dependent; see references/INDEX.md.
  • Not for delete, CI association, conflict-checking, scheduling, or change-task endpoints — no platform procedure under this skill covers those.

Universal concepts (common ITSM change-management vocabulary, not a wire standard)

Unlike a protocol-grounded skill (e.g. DNS/RFC 1035), there is no single spec every change-management platform implements — this section states practice-level concepts common across ITSM tooling, not RFC-derived rules. Not every concept below is guaranteed on every platform — confirm against references/INDEX.md before assuming a capability exists:

  • A change moves through named states, but "how do I know what's next" varies by platform. ServiceNow gates transitions with a dedicated readiness check; Jira exposes a "get available transitions" list (discoverable, but not a readiness gate — it just says what the workflow currently permits); Freshservice and BMC treat status as a plain field with no discovery mechanism documented in the sources. Where no gate/discovery is documented, the calling agent is responsible for sequencing status changes sensibly — the API itself won't stop an out-of-order one.
  • Approve/reject capability is a spectrum, not binary — check the specific platform. ServiceNow lets this skill submit the approval decision directly on anyone's behalf (permission allowing). Jira allows an API-driven approve/decline, but strictly for the credential matching the assigned approver, and only once (no re-decision). Freshservice restricts the API to observing approval state and cancelling a pending request — approve/reject can only be done by the approver in the product itself. Check references/INDEX.md before promising any specific approve/reject capability to the caller; if the target platform doesn't support what's being asked, say so rather than attempting a workaround.
  • Approval and state are related but distinct. A change can be approved but not yet in a closable state, or vice versa depending on the platform's model — check both explicitly rather than assuming one implies the other.
  • Close (or the platform's equivalent terminal state) is effectively irreversible. Every platform procedure under this skill treats it as a required operator-confirmation point.
  • Cancelling a pending approval is not the same as rejecting it. Where a platform only supports cancellation (no reject), report the outcome as CANCELLED, not REJECTED — cancelling means the request was withdrawn, not that an approver declined it.
  • Rejection, where supported, has real process consequences beyond just "not approved" (e.g. auto-cancelling dependent tasks) — treat it as its own confirmation point, not a lesser version of approval.

Procedure

  1. Identify the target platform — from the caller's request or the platform argument. If it isn't one of the platforms in references/INDEX.md, stop: this skill doesn't cover it yet.
  2. Open references/<platform>/procedure.md and follow it exactly — it contains that platform's full operational procedure, error handling, patterns, known limitations, tools, and verification checklist.
  3. Report the outcome using that platform procedure's own status vocabulary — don't normalize it away.

Known limitations

  • Currently covers ServiceNow, Freshservice, Jira Service Management, and BMC Helix ITSM — see references/INDEX.md for exactly which actions each supports (they are not symmetric — see Universal concepts above). A platform not listed there needs a new references/<platform>/procedure.md before this skill can be used for it.
  • Does not cover delete, CI association, conflict-checking, scheduling, or change-task endpoints on any platform.
  • Approve/reject-by-API is platform-dependent, not guaranteed — check references/INDEX.md before telling a caller this skill can approve or reject a change on their behalf.

Contributing to this skill

SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or adding a pointer to a newly-supported platform. Platform-specific procedure changes — a new error code, a corrected field, a changed API path — belong in that platform's own references/<platform>/procedure.md and endpoints.md, never here.

Tools

Each platform assumes its own authenticated client — see references/INDEX.md for which, and that platform's procedure.md for the specific operations.

Verification checklist

  • Target platform confirmed against references/INDEX.md before proceeding
  • That platform's own procedure.md was followed, including its own confirmation gates and error handling — not a generic/improvised sequence
  • Outcome reported using the platform procedure's own status vocabulary

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.