agentleFS
Sign inStart free
opsmillopsmill/infrahub/.agents/skills/speckit-agent-context-update/SKILL.md

speckit-agent-context-update

Skill548 starsChanged 9 days agoApache-2.0View on GitHub

Refresh the managed Spec Kit section in coding agent context file(s)

12 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    If context_files and context_file are empty, the command reports nothing to do and exits successfully.

    line 25
  2. Very specific:

    When plan_path is omitted, the script auto-detects the most recently modified specs/*/plan.md.

    line 32

“Common” is measured: kept by at least 6 in 10 of the 11 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

Update Coding Agent Context

Refresh the managed Spec Kit section inside the active coding agent's context/instruction file (e.g. CLAUDE.md, .github/copilot-instructions.md, AGENTS.md).

Behavior

The script reads the agent-context extension config at .specify/extensions/agent-context/agent-context-config.yml to discover:

  • context_file — the path of the coding agent context file to manage.
  • context_files — optional project-relative paths for multiple coding agent context files. When non-empty, the script updates each listed file and the list takes precedence over context_file.
  • context_markers.start / .end — the delimiters surrounding the managed section. Defaults to <!-- SPECKIT START --> and <!-- SPECKIT END --> when the field is missing.

It then creates, replaces, or appends the managed block so that the section points at the most recent plan path when one can be discovered (specs/<feature>/plan.md).

If context_files and context_file are empty, the command reports nothing to do and exits successfully. Context file paths must stay project-relative; absolute paths, Windows drive paths, backslash separators, and .. path segments are rejected.

Execution

  • Bash: .specify/extensions/agent-context/scripts/bash/update-agent-context.sh [plan_path]
  • PowerShell: .specify/extensions/agent-context/scripts/powershell/update-agent-context.ps1 [plan_path]

When plan_path is omitted, the script auto-detects the most recently modified specs/*/plan.md.

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