Automated summary
Implements and applies an approved change proposal by following a structured process.
Strengths
- Encourages minimal and focused implementations
- Follows a clear sequence of steps with task tracking
- References multiple documents for full context
Limitations
- Requires a specific directory structure (changes/<id>)
- Depends on the prompter tool for commands and context
Use this skill when you need to implement a pre-approved change with clearly defined tasks.
Do not use it for exploratory or unplanned changes that require creativity and back-and-forth.
Security analysis
SafeThe skill instructs reading and editing files, updating checklists, and using internal tooling; no destructive or exfiltrating actions are present.
No concerns found
How this analysis is madeExamples
Apply the change proposal with id 42. Read the proposal, design, and tasks files, then implement the changes step by step.I want to implement the tasks listed in changes/15/tasks.md. Please follow the apply skill process.name: apply description: Implement and apply an approved change proposal
<!-- PROMPTER:START -->Guardrails
- Favor straightforward, minimal implementations first and add complexity only when it is requested or clearly required.
- Keep changes tightly scoped to the requested outcome.
- Refer to
prompter/AGENTS.md(located inside theprompter/directory—runls prompterif you don't see it) if you need additional Prompter conventions or clarifications.
Steps Track these steps as TODOs and complete them one by one.
- Read
changes/<id>/proposal.md,design.md(if present), andtasks.mdto confirm scope and acceptance criteria. - Work through tasks sequentially, keeping edits minimal and focused on the requested change.
- Confirm completion before updating statuses—make sure every item in
tasks.mdis finished. - Update the checklist after all work is done so each task is marked
- [x]and reflects reality. - Reference
prompter listorprompter show <item>when additional context is required.
Reference
- Use
prompter show <id> --json --deltas-onlyif you need additional context from the proposal while implementing.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/apply-an-approved-change-proposal-mrwak9xf/download' --output '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md.part' && mv '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md.part' '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md' && test -s '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/apply' && cp -R '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf' '.claude/skills/apply'Cursor
test -f '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md' && test -s '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/apply' && cp -R '.skill-downloads/apply-an-approved-change-proposal-mrwak9xf' '.cursor/skills/apply'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/apply-an-approved-change-proposal-mrwak9xf'openskills read 'apply-an-approved-change-proposal-mrwak9xf'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/apply-an-approved-change-proposal-mrwak9xf/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.