Coordinate safe, audited changes to the instar source tree.
npx skills add https://github.com/JKHeadley/instar --skill instar-dev
Please help me install this Agent Skill. Skill: instar-dev Source: https://github.com/JKHeadley/instar/tree/main/skills/instar-dev Command: npx skills add https://github.com/JKHeadley/instar --skill instar-dev
This Skill gives the instar-developing agent a safe, enforced workflow for changing the instar repository without skipping the reviews, traces, and gates that protect every downstream agent.
Use the instar-dev skill to make a compliant change to the instar source tree, then complete the required review artifact and trace before committing.
High-intent search queries and answers about installing and using this skill.
To enforce safe repository updates, you need a structured change process that wraps development in required phases for principle checking, planning, build execution, side-effects review, and trace writing. This ensures runtime behavior changes are fully audited.
Side-effects review is a mandatory validation phase needed when modifying runtime code, hooks, or templates to prove downstream impacts were analyzed. It acts as a commit gate to prevent unreviewed behavior changes from slipping through.
You add trace logging by completing the required trace writing phase after build execution and side-effects review. This produces the necessary audit artifacts that verify hook-compliant commit and push behavior for repository changes.
No, no-deferrals enforcement explicitly prevents partial fixes from passing. Spec prerequisites and signal-vs-authority checks must be fully satisfied, requiring second-pass review for any high-risk changes before commit gating allows the update.
Yes, the process is designed for changes to runtime code, hooks, jobs, templates, and remediation runbooks. An agent updating a recovery path uses it to make the change, prove side effects were reviewed, and produce required commit artifacts.
Repository enforcement requires second-pass review because high-risk changes to runtime behavior and hooks impact every downstream agent. Signal-vs-authority checks and spec validation ensure changes are verified and no partial fixes slip through.
davidleeCreate or update spec revisions when requirements move between source and destination specs.
sunLeeeValidate changes and generate conventional-commit messages for Git push workflows.
infolog-ioSelect execution architectures for AI skills based on workflow complexity and portability.
ajsai47Automate end-to-end code shipping with merging, tests, versioning, and PRs.
