schedule-instruction-review

Tightens repository instruction files and lands cuts as a draft pull request.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/JSdotNet/devbook --skill schedule-instruction-review-jsdotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schedule-instruction-review
Source: https://github.com/JSdotNet/devbook/tree/main/plugins/delivery-schedule/skills/schedule-instruction-review
Command: npx skills add https://github.com/JSdotNet/devbook --skill schedule-instruction-review-jsdotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Instruction assets like AGENTS.md, rules, skills, and prompts grow endlessly because nobody deletes sentences, until the model attends to none of them. This Skill applies a scheduled deletion discipline that cuts dead weight and lands changes where a person can review them file by file. ## Core Features & Use Cases - Sentence-level audit: Walks every instruction file and classifies findings as no-op, duplicate, prohibition, slop, dead-pointer, or over-budget, with a cut, rewrite, or report action per hit. - Review-safe delivery: Opens one draft pull request with one commit per file and a ledger of every cut, so a reviewer can drop a single file without losing the rest. - Rejection memory: Skips any file touched by a previously rejected instruction-review pull request, so the run converges instead of re-proposing refused cuts. - Use Case: Run weekly against a repository whose AGENTS.md and skill files have bloated over months; receive a draft PR trimming redundant rules and fixing dead pointers, with protected frontmatter and managed sections untouched. ## Quick Start Ask the agent to run the scheduled instruction review with default scope and rewrites enabled, then review the resulting draft pull request.

Frequently Asked Questions about schedule-instruction-review

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

FAQPage Schema
How do I reduce bloat in AGENTS.md and AI instruction files?▼

Run a scheduled instruction review that walks each file sentence by sentence, classifies findings as no-ops, duplicates, prohibitions, slop, or dead pointers, and applies cuts. Changes land as one draft pull request with one commit per file for review.

How to automate instruction file cleanup with pull requests?▼

Use the gh CLI to open a draft pull request titled chore(instructions): tighten <date>, carrying a ledger table of lines before and after per file. Draft status keeps a human re-read as the verification step since no check proves a rewritten instruction.

Can the review rewrite sentences or only cut them?▼

Both modes exist: the Rewrites input defaults to true, enabling rewrites such as turning prohibitions positive, while setting it to false applies cuts only. Running cuts-only first shows whether the standard fits the repository before rewrites change meaning.

What content is protected from instruction tightening edits?▼

Frontmatter, code fences, managed sections, and anything under .devbook/ are never edited. Findings inside protected text become report-only entries, and over-budget files are reported rather than cut to fit.

Why are files skipped after a rejected pull request?▼

A closed, unmerged pull request from a prior instruction-review run counts as a rejection, and its files are skipped in future runs. This treats rejection as an answer so the run converges instead of repeatedly proposing refused cuts.