agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/azuremonitor-opentelemetry-profiler-net/.github/skills/bump-submodule-ref/SKILL.md

bump-submodule-ref

Skill6 starsChanged 6 months agoMITView on GitHub

Bump the ServiceProfiler submodule reference in the main repo. Use this skill when asked to bump, update, or sync the ServiceProfiler submodule reference. Handles validation, commit, tagging, and push.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    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:

    Run git -C ServiceProfiler log --oneline -1 to show the current submodule HEAD.

    line 14
  2. Distinctive:

    Run git diff --submodule ServiceProfiler to show what changed.

    line 15
  3. Distinctive:

    Ask the user to confirm before proceeding.

    line 16
  4. Distinctive:

    Run git -C ServiceProfiler status --porcelain in the repo root.

    line 19
  5. Distinctive:

    If there are uncommitted changes, stop and tell the user to commit or stash them first.

    line 20
  6. Distinctive:

    Always confirm with the user before committing or pushing.

    line 33

≈ “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

Bump ServiceProfiler Submodule Reference

Steps

  1. Show current state and confirm with user before proceeding:
    • Run git -C ServiceProfiler log --oneline -1 to show the current submodule HEAD.
    • Run git diff --submodule ServiceProfiler to show what changed.
    • Ask the user to confirm before proceeding.
  2. Verify ServiceProfiler repo is clean:
    • Run git -C ServiceProfiler status --porcelain in the repo root.
    • If there are uncommitted changes, stop and tell the user to commit or stash them first.
  3. Commit the submodule reference update in the main repo:
    • Run git add ServiceProfiler
    • Run git commit -m "Bump ServiceProfiler submodule reference"
  4. Tag and push using the script:
    • On Windows: & .github/skills/bump-submodule-ref/scripts/tag-submodule.ps1
    • On Linux/macOS: bash .github/skills/bump-submodule-ref/scripts/tag-submodule.sh
    • The script validates the submodule is clean, creates tag otel-profiler-ref-<short-hash>, and pushes it.

Notes

  • Always confirm with the user before committing or pushing.
  • The tag format is otel-profiler-ref-<short-hash>.
  • The repo root is C:\AIR\fork-otel-profiler.

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