skills.rest
torikhayes
torikhayesCOMMUNITY
Explore all skills by this author →
GitHub

update-context

Syncs .github/context/ documentation files after code changes by executing a shared agent workflow.

Updated Jul 13, 2026
Search Tags:#documentation#pull request#agent workflow#code changes#context sync#github copilot#architecture docs
One-click install
npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill update-context-torikhayes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-context
Source: https://github.com/torikhayes/aeai-dotnet-brownfield/tree/main/.claude/skills/update-context
Command: npx skills add https://github.com/torikhayes/aeai-dotnet-brownfield --skill update-context-torikhayes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing a feature or merging a branch, project context and architecture documentation in .github/context/ often becomes stale. This Skill keeps those context files synchronized with the actual codebase so documentation never drifts from reality. ## Core Features & Use Cases - Context Synchronization: Updates the .github/context/ files to reflect recent code changes before opening a PR or after merging. - Shared Agent Workflow: Delegates to the single source of truth at .github/agents/update-context.agent.md, which is shared with GitHub Copilot, avoiding duplicated instructions. - Flexible Diff Scope: Accepts an optional branch name or specific files to diff against, defaulting to comparing HEAD against origin/main. - Use Case: You just finished implementing a new checkout service. Before opening your pull request, invoke this Skill to refresh the architecture and context docs so reviewers see accurate documentation. ## Quick Start Ask the assistant to update the context files and sync the docs after your latest code changes, optionally naming a branch to diff against.

Frequently Asked Questions about update-context

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update stale context documentation after code changes?▼

Invoke the update-context Skill after finishing a feature or before opening a PR. It reads the workflow in .github/agents/update-context.agent.md and syncs the .github/context/ files to match your recent code changes.

How do I diff context updates against a specific branch?▼

Pass an optional branch name or specific files as an argument when invoking the Skill. By default it compares HEAD against origin/main to determine which changes need to be reflected in the context files.

When should I run the context sync workflow?▼

Run it after completing a feature, before opening a pull request, after merging a branch, or whenever the context files appear stale. These trigger points keep architecture documentation aligned with the codebase.

Does this Skill work with GitHub Copilot?▼

Yes. The Skill delegates to .github/agents/update-context.agent.md, which is explicitly shared with GitHub Copilot as the single source of truth, so both tools execute the same workflow without duplicated instructions.

What are the limitations of the update-context workflow?▼

The Skill itself contains no logic; it depends entirely on the instructions in .github/agents/update-context.agent.md. If that agent file is missing or incomplete, the Skill cannot perform the synchronization.

Related Skills

Explore More Software Engineering Skills→
imvanzenimvanzen

commit-series-on-branch

Creates commits on-demand from GitHub and/or GitLab events and webhooks. Fetches metadata for each commit and forwards it to the specified URL.

Community
Advanced
hollis-labshollis-labs

workflow-docs-review

Refresh the Project Context Cache and apply minimal documentation updates.

Official
Advanced
hardisgroupcomhardisgroupcom
368

test

Build, lint, and test code changes with yarn commands.

Official
Intermediate
lasswelltlasswellt
1

doc-gen

Generate project documentation from source code for Vue/Nuxt projects.

Community
Advanced