Menu
Repository maintenance and coding-agent instructions for AI-Assistant.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | repo-guidelines |
| description | Repository maintenance and coding-agent instructions for AI-Assistant. |
| license | MIT |
This skill contains repository maintenance guidance and coding-agent operating rules for AI-Assistant.
AGENTS.md is the general guide for coding agents working in this repository.CLAUDE.md is the Claude-specific behavior and workflow guide..github/skills/*/SKILL.md file for the subsystem being changed.Bridge the ComfyUI anime image pipeline into the chat SSE stream so image generation renders inline in the chat bubble. Use when: changing how image-generation events reach the chat UI, editing the force_image_bridge gate or the SSE forwarder in stream.py, touching cancel / GPU-leak handling (GeneratorExit → request_cancel → /free), the error_class taxonomy, the Phase 1b thinking-block nesting, or the Phase 3 WS live-preview; debugging why an image turn stalls, double-renders, leaks VRAM, or shows the wrong error; or running the PR4 verification harness. This subsystem deliberately spans services/chatbot/ AND app/image_pipeline/.
Choose which repository skill to activate for a given task. Use when: starting any chatbot, MCP, config, or docs task to determine the best skill or skill combination; reviewing whether the right skills were applied; or deciding whether to combine multiple skills for a cross-cutting change.
Reason about the impact of chatbot/core changes on GitHub workflows, tests, security scans, and CI behavior. Use when: adding or changing routes, tools, providers, or dependencies; reviewing a PR that might affect CI; debugging CI failures after a chatbot change; checking whether a code change needs a workflow or docs update; or auditing workflow assumptions after startup or env changes.
Map changed files to the smallest sufficient verification set. Use when: deciding which tests to run after a code change, explaining why a test scope is enough, or choosing between unit tests, integration tests, and manual checks.
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki"
Keep documentation aligned with runtime behavior. Use when: changing ports, entry points, startup commands, env variables, service responsibilities, or removing/renaming scripts. Requires a runtime-vs-docs comparison before finalizing any change that alters observable behavior.