update-context

Update KANBAN and architecture documentation after completing development tasks with GitHub integration.

Updated May 11, 2026
One-click install
npx skills add https://github.com/TomasGC/Meerkat --skill update-context-tomasgc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-context
Source: https://github.com/TomasGC/Meerkat/tree/main/skills/update-context
Command: npx skills add https://github.com/TomasGC/Meerkat --skill update-context-tomasgc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After finishing development work, developers often forget to update project documentation, leaving KANBAN boards stale and GitHub issues without technical context. This Skill automates post-task documentation updates so project records stay accurate and cumulative. ## Core Features & Use Cases - KANBAN Entry Management: Creates or updates one cumulative entry per issue in contexts/kanban.md with strict formatting rules for dates, tags, refs, and commits. - GitHub Issue Commenting: Adds structured technical comments (work completed, files modified, tests, commits) to GitHub issues after user confirmation. - Architecture & Rules Updates: Updates architecture.md for design changes and creates reusable rules files when new coding patterns are discovered. - Use Case: After merging a payment feature branch, run the skill to update the [#123] KANBAN entry with new commits, post a technical summary comment to the GitHub issue, and document the new repository pattern in the architecture context. ## Quick Start Tell the assistant to update the project context and documentation for the task you just finished, providing the ticket ID and commit hashes.

Frequently Asked Questions about update-context

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

FAQPage Schema
How do I update a KANBAN board after finishing a coding task?

Provide the ticket ID, commit hashes, and a brief work description. The skill searches for an existing entry for that ticket and updates it cumulatively, or creates a new entry at the top following the YYYY-MM-DD - [TICKET-ID] Title format.

How to add technical comments to GitHub issues automatically?

The skill uses the GitHub CLI integration to fetch issue details and add a structured comment covering work completed, implementation details, files modified, tests, and commits. It always asks whether to add, edit, or skip the comment first.

Does the skill create duplicate KANBAN entries for the same ticket?

No. It enforces one entry per issue by searching for the existing [TICKET-ID] before writing. Existing entries are updated with a new date, merged cumulative description, and appended commit hashes.

What happens if the GitHub issue is not found?

The skill warns that the ticket was not found and offers to continue updating only the local KANBAN.md without a GitHub link, or to verify the issue number. The rest of the documentation workflow proceeds normally.

When should architecture documentation be updated after a task?

Update architecture.md only when the work introduced new modules or services, changed design patterns, modified the technology stack, or significantly altered data models. Minor fixes and formatting changes should not trigger architecture updates.