Automated summary
This skill enforces a read-only repository audit (active phase file, handoff manifest, readFirst paths) before any code change, and outputs a file-by-file edit plan.
Strengths
- Forces the agent to read the active phase file and handoff/realignment/manifest.json before writing anything
- Surfaces existing contracts and conflicts with the phase objective, catching silent regressions early
- Explicitly lists files to edit, tests to add, validation commands, and a risks section
- Standardized markdown output (Phase audit summary) that is easy to review or attach to a PR
Limitations
- Tightly coupled to a specific MCOS layout (handoff/realignment/manifest.json, phase files with readFirst), so it is not portable as-is
- No automated analysis tooling: audit quality depends entirely on what the agent reads manually
- It provides no technical guard preventing edits; the "no edits before the plan" rule relies on agent discipline
Invoke it manually at the start of each phase, right before touching the repository, to frame the edits and validation steps.
Unnecessary for a one-off fix or a read-only exploration that does not follow the MCOS phase workflow.
Security analysis
SafeThe skill only instructs reading files and producing an audit plan. It declares no tools and does not direct any execution, modification, network access, or destructive actions. No sensitive data handling or exfiltration risk is present.
No concerns found
How this analysis is madeExamples
/repo-audit — audit the repo for phase 3 before I change anything, and give me the edit plan with tests and validation commands.Run the repo audit: read the active phase file and handoff/realignment/manifest.json, then list any old contracts that conflict with the phase objective.Before I implement, audit the phase readFirst paths and produce the files-to-edit, tests-to-update, validation-commands and risks summary.name: repo-audit description: Audit MCOS repository state before implementing a phase. Use before edits in every phase. disable-model-invocation: true
Repo Audit Skill
Use this before editing.
- Read the active phase file.
- Read
handoff/realignment/manifest.json. - Inspect all phase
readFirstpaths. - Identify old contracts that conflict with the phase objective.
- Produce a file-by-file edit plan.
- Identify tests and validation commands before editing.
- Do not edit until the plan is explicit.
Output:
## Phase audit summary
- Phase:
- Existing contracts found:
- Conflicts:
- Files to edit:
- Tests to update/add:
- Validation commands:
- Risks:
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/repo-audit-ms47voar/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/repo-audit-ms47voar' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/repo-audit-ms47voar/download' --output '.skill-downloads/repo-audit-ms47voar/SKILL.md.part' && mv '.skill-downloads/repo-audit-ms47voar/SKILL.md.part' '.skill-downloads/repo-audit-ms47voar/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/repo-audit-ms47voar/SKILL.md' && test -s '.skill-downloads/repo-audit-ms47voar/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/repo-audit' && cp -R '.skill-downloads/repo-audit-ms47voar' '.claude/skills/repo-audit'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/repo-audit-ms47voar'openskills read 'repo-audit-ms47voar'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/repo-audit-ms47voar/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.