← ClaudeAtlas

github-instructions-ai-control-file-implement-instructionslisted

Imported repository guidance from .github/instructions/ai-control-file-implement.instructions.md. Use when working in this repository and the original guidance is relevant.
Tempuskg/session-control · ★ 1 · AI & Automation · score 74
Install: claude install-skill Tempuskg/session-control
Follow this imported repository guidance from `.github/instructions/ai-control-file-implement.instructions.md` when the task overlaps with its original scope. ## Instructions - Treat the guidance below as repository-specific instructions for this project. - Apply it together with higher-priority system, developer, and repo instructions already in effect. - Preserve the intent of the source guidance while adapting it to the current task. ## Imported guidance # AI Control File Implementation - Read `AGENTS.md`, `.github/copilot-instructions.md`, and any user-named analysis report before the first edit. Read `package.json` only when the task depends on commands, contribution points, versioning, or release metadata. - Start the first implementation reply with `External instructions:` followed by each user-referenced out-of-repo instruction file and one status: `accessible/applied`, `accessible/ignored`, `inaccessible`, or `out-of-scope`. If none were referenced, say `External instructions: none`. - Inspect `git status --short` and `git diff -- <candidate AI files>` before editing. - Before the first edit, use at most one repo-wide search and one targeted search. Skip directory listings or wildcard scans when exact AI-control-file paths are already known. - If the current surface lacks tool or workspace access, use handoff-first behavior instead of claiming direct implementation. - Make the smallest safe AI-control-file edit in the same turn. If that is not possible, return on