Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
Bootstraps a project's tool-agnostic AGENTS.md files for a greenfield project, an undocumented codebase or one area, adding only what is missing and never overwriting curated content.
Install Project Context Auditor
$ npx skills add jsmastery-pro/skills --skill audit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jsmastery-pro/skills audit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jsmastery-pro/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/audit .claude/skills/audit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "audit" agent skill from https://github.com/jsmastery-pro/skills/tree/main/skills/audit into .claude/skills/audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jsmastery-pro/skills/tree/main/skills/auditType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jsmastery-pro/skills --skill audit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jsmastery-pro/skills audit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jsmastery-pro/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/audit .agents/skills/audit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "audit" agent skill from https://github.com/jsmastery-pro/skills/tree/main/skills/audit into .agents/skills/audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jsmastery-pro/skills --skill audit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jsmastery-pro/skills audit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jsmastery-pro/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/audit .cursor/skills/audit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "audit" agent skill from https://github.com/jsmastery-pro/skills/tree/main/skills/audit into .cursor/skills/audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jsmastery-pro/skills.git --path skills/audit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jsmastery-pro/skills --skill audit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jsmastery-pro/skills audit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jsmastery-pro/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/audit .gemini/skills/audit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "audit" agent skill from https://github.com/jsmastery-pro/skills/tree/main/skills/audit into .gemini/skills/audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jsmastery-pro/skills auditInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jsmastery-pro/skills --skill audit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jsmastery-pro/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/audit .github/skills/audit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "audit" agent skill from https://github.com/jsmastery-pro/skills/tree/main/skills/audit into .github/skills/audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jsmastery-pro/skills --skill audit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jsmastery-pro/skills audit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jsmastery-pro/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/audit .opencode/skills/audit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "audit" agent skill from https://github.com/jsmastery-pro/skills/tree/main/skills/audit into .opencode/skills/audit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "audit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
audit- GitHub stars
- 1.4k
- Token cost
- ~3.2k tokens
- SKILL.md length
- 1,815 words
- Files
- 12
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Bootstraps a project's tool-agnostic AGENTS.md files for a greenfield project, an undocumented codebase or one area, adding only what is missing and never overwriting curated content.
- Works in 5 steps: Context files: root AGENTS.md present →… → Source count across common ecosystems… → Established signals: git log --oneline… → …
- Bootstrapping AGENTS.md files for a brand-new, unscaffolded project
- SKILL.md covers Output style (plain words, no…, What this skill does, Context file convention… and Scope, plus 6 more sections
- Calls git
What it does
The skill runs in one of three modes depending on the project's state: for a greenfield project with no code yet, it asks for coding standards and seeds a root AGENTS.md from the answers plus the build approach; for an undocumented codebase, it scans the whole project and writes a root AGENTS.md plus nested area-specific files, judging what belongs globally versus locally; for a partially documented codebase, it compares existing docs with the code and adds only missing global facts or docs for undocumented areas, never clobbering curated content. It does not create specs, maintain files later or write feature scope; sibling skills own those jobs.
AGENTS.md is the canonical, tool-agnostic file every agent reads, while CLAUDE.md stays a one-line pointer that imports the sibling AGENTS.md rather than duplicating its content; a CLAUDE.md with real content but no AGENTS.md is migrated only after asking permission. Output style is also a hard constraint: everything the skill writes avoids dashes and hyphens as punctuation, spelling out words like read only instead, while code, file paths and command flags keep their hyphens untouched.
When your agent uses it
- Bootstrapping AGENTS.md files for a brand-new, unscaffolded project
- Backfilling documentation for an existing codebase that has none
- Filling documentation gaps in one area of a partially documented project
Example prompts
- “Run /audit on this fresh project to seed its root AGENTS.md.”
- “Audit src/auth and fill in whatever AGENTS.md context is missing there.”
- “Scan the whole repo and write nested AGENTS.md files for each undocumented area.”
Requirements
- Pre-approved tools (allowed-tools): Bash, Read, Grep, Glob, Write, Edit, Agent, AskUserQuestion
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Context files: root AGENTS.md present → ROOT_EXISTS; a CLAUDE.md with content only → ROOT_LEGACY; neither → ROOT_MISSING.
- Source count across common ecosystems (extensions like .ts/.tsx/.js/.jsx/.py/.go/.rs/.java/.rb/.swift/.kt/.php/.cs/.dart/.ex/.exs/.scala/.c…
- Established signals: git log --oneline for commit history depth; a real manifest (package.json, pyproject.toml, go.mod, Cargo.toml…
- Monorepo signal: workspace markers (pnpm-workspace.yaml, turbo.json, a "workspaces" field in package.json) or any apps/*/package.json /…
- Workflow setup signal (WORKFLOW_SETUP): root AGENTS.md is MISSING while the workflow has already decided the stack, i.e. a docs/specs/…
What it can do on your machine
Read from SKILL.md and the folder at commit 43b69e4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGrepGlobWriteEditAgentAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Project Context Auditor loads about 3.2k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 1,815 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Grep, Glob, Write, Edit, Agent, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jsmastery-pro/skills at commit 43b69e4, republished under its MIT licence (© jsmastery-pro). 1,815 words, ~3,232 tokens.
Download SKILL.mdSave it as
.claude/skills/audit/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.- name
- audit
- description
- Run /audit on a greenfield project, an existing codebase with missing docs, or one area (/audit src/auth) to bootstrap the project's AI context, the AGENTS.md files every later skill reads. Writes tool agnostic AGENTS.md plus thin CLAUDE.md pointers, adding only what is missing; never overwrites curated content.
- allowed-tools
- Bash, Read, Grep, Glob, Write, Edit, Agent, AskUserQuestion
Output style (plain words, no dashes, no hyphens)
<!-- OUTPUT-STYLE:START -->Write everything this skill produces, files and messages alike, in plain simple language. Talk to the reader as you, warm and direct like a colleague, and present every step as a recommendation they may run or skip, never an order. Keep technical terms that carry real meaning; explain each in plain words. Never use a dash or a hyphen as punctuation: no em dash, no en dash, and no hyphenated compounds. Write read only, not read-only. Say it in simple words, or reword the sentence. Code, file paths, command flags, and values other skills match on keep their hyphens. Use short sentences, commas, or parentheses. Clear beats clever.
<!-- OUTPUT-STYLE:END -->What this skill does
The context bootstrapper: writes the AGENTS.md files every later skill and AI tool reads.
- Greenfield (no code yet): ask for coding standards, seed root
AGENTS.mdfrom the answers plus the build approach (name and one line principle) from the scope header if/scopeset one. Runs after the project is scaffolded with its chosen stack (/scope→/architectdecides the stack → scaffold →/audit); earlier is premature. - Brownfield, undocumented (code, no
AGENTS.md): scan the whole project, write rootAGENTS.mdand nested<area>/AGENTS.mdfiles, judging what is global (root) vs area specific (nested). - Brownfield, partially documented: check existing root and nested docs against the whole codebase; add only what is missing (new global facts, nested docs for undocumented areas); never clobber curated content.
Does not create specs (/architect owns those), maintain files after changes (/sync owns that), or write the feature scope (/scope owns docs/scope/).
Context file convention (AGENTS.md is canonical)
Durable context lives in the tool agnostic AGENTS.md (root and nested); every agent (Codex, Cursor, Claude Code, and others) reads it. CLAUDE.md is only a one line pointer whose entire body imports the sibling AGENTS.md via Claude Code's @ import (exact pointer body in agent-prompt.md); content is never duplicated across the two.
- Write knowledge into
AGENTS.md. Create it when missing. Never overwrite an existingAGENTS.md(it may be user or tool authored); gap fill conservatively, with permission. - Migrate legacy content: a
CLAUDE.mdwith content but noAGENTS.md→ ask permission, move its content into a newAGENTS.md, replaceCLAUDE.mdwith the pointer. Never silently discard curated content. - Root stays short and global; nested
AGENTS.mdonly for meaningful areas with real conventions (same root/nested rules as previously applied toCLAUDE.md).
Scope
An area path argument (e.g. auth, src/payments) triggers Phase 3. With no argument, the Pre-flight signals below route to Phase 0 (ambiguous: ask new vs existing), Phase 1 (greenfield: ask standards, seed root), Phase 2 (established, no root AGENTS.md: whole-repo scan), or Phase 4 (root AGENTS.md exists: gap-fill). A legacy CLAUDE.md with content but no AGENTS.md is migrated, then treated as Phase 4.
Acts vs asks
Phase 1 asks coding standards questions via MCQ before creating root AGENTS.md. Phase 2 acts immediately, no questions; it writes root and the nested docs it judges warranted. Phases 3 and 4 act to explore but ask permission before modifying an existing root AGENTS.md or migrating a legacy CLAUDE.md; Phase 4 reports nested doc creation for undocumented areas first, then applies on confirmation.
Artifact ownership
The AGENTS.md files hold the content: create root if missing (Phase 1, 2) and <area>/AGENTS.md if missing and warranted, by judgment (Phase 2, 3, 4); when one exists, gap-fill or propose additions with permission; never overwrite. The CLAUDE.md files are pointers only (root and area), created if missing; a legacy one with content is migrated into AGENTS.md with permission. When creating a nested AGENTS.md, add exactly one pointer line to root AGENTS.md under ## Context files: - [<area>/AGENTS.md](<area>/AGENTS.md) (<one-line description>). Never one per subfolder, only where distinct conventions exist.
Portability (any OS, any agent)
- Commands:
gitis the only required CLI, same on every OS. Other shell snippets (file counts,find,[ -f ]) are POSIX reference, not literal scripts; use your agent's cross platform file tools (search/glob, read, write) to list, count, and check existence. - Bundled files live in this skill's folder:
agent-prompt.md, the phase mode files (modes/*.md), and the pattern presets (patterns/*.md). Resolve the folder to an absolute path. Read the matching phase mode file when routing, thenagent-prompt.mdplus the SELECTED pattern preset at write time. Its ALL_CAPS placeholders (PHASE, AREA, ADDITIONAL_STANDARDS, MONOREPO_OR_NO, INSTALLED_SKILLS, DECLINED_TOOLS, and so on) are the inputs you gathered in pre-flight and the question rounds; apply each as you read. - No interactive question support? Ask any multiple choice question as plain text with the same options.
Execution
The main thread does the writing in every phase; it never hands AGENTS.md writing to a subagent. The only subagent is a read only scout (cheapest model, Claude Code: haiku, never the session model), spawned only for a large scan; it returns a compact map the main thread writes from. A small scaffold or single area needs no scout; read it directly. Right before writing, read agent-prompt.md (persona, per phase instructions, templates) plus, in Phase 1, the selected pattern preset; then write following it. Read agent-prompt.md only at write time, not during pre-flight.
Show full SKILL.md (975 more words)Show less
Pre-flight (main thread does this before anything else)
Gather several signals (a file count alone misleads: a scaffold inflates it, an unfamiliar language zeroes it):
- Context files: root AGENTS.md present →
ROOT_EXISTS; a CLAUDE.md with content only →ROOT_LEGACY; neither →ROOT_MISSING. - Source count across common ecosystems (extensions like
.ts/.tsx/.js/.jsx/.py/.go/.rs/.java/.rb/.swift/.kt/.php/.cs/.dart/.ex/.exs/.scala/.c/.cpp/.h/.lua/.clj), excluding vendored/generated dirs (node_modules,.git,dist,build) and config files (*.config.*). - Established signals:
git log --onelinefor commit history depth; a real manifest (package.json,pyproject.toml,go.mod,Cargo.toml,composer.json,*.csproj,pubspec.yaml,mix.exs,Gemfile). - Monorepo signal: workspace markers (
pnpm-workspace.yaml,turbo.json, a"workspaces"field inpackage.json) or anyapps/*/package.json/packages/*/package.jsonnear the root. - Workflow setup signal (
WORKFLOW_SETUP): root AGENTS.md is MISSING while the workflow has already decided the stack, i.e. adocs/specs/architecture spec exists (a## Proposed stacksection), and/ordocs/scope/has a "Stack and architecture" (or similar foundational scaffold) feature. This is the intended greenfield order (/scope→/architectdecides the stack →/developscaffolds it →/audit): freshly scaffolded, still needs coding standards captured. When it fires, the manifest and scaffold source that now exist are the scaffold, not a existing codebase.
Pick the phase. The order of checks matters: the workflow setup signal outranks the raw code count, because a fresh scaffold has a manifest and source files yet is still greenfield.
| Condition | Phase |
|---|---|
| Area path given as argument | Phase 3 |
ROOT_EXISTS (or ROOT_LEGACY after migration) | Phase 4 |
ROOT_MISSING and WORKFLOW_SETUP (stack spec and/or scope stack feature) | Phase 1, even though a manifest and scaffold source now exist. Ask the coding standards; seed root from the spec's stack. Never treat a just scaffolded workflow project as brownfield. |
ROOT_MISSING, no WORKFLOW_SETUP, no source files AND no manifest | Phase 1 |
ROOT_MISSING, no WORKFLOW_SETUP, has code (source ≥ 10 or a manifest), ≥ 2 commits and clearly real feature code (not just scaffold) | Phase 2, any language |
ROOT_MISSING, no WORKFLOW_SETUP, has code but it looks like untouched scaffold, or ≤ 1 commit, or you can't tell greenfield from brownfield | Phase 0, ask |
Why this order: a fresh scaffold has a manifest and starter files but is still greenfield, so a raw code count alone would misread it as brownfield and skip the standards questions; the workflow setup signal catches that and routes to greenfield. Truly brownfield (Phase 2) means real feature code, real history, and no workflow setup in progress. Anything ambiguous falls to Phase 0; never default a maybe greenfield project to brownfield.
Monorepo (MONOREPO=yes): root plus a light stub per workspace, deepen on demand. Each workspace (apps/*, packages/*) is a first class area; its primary doc lives at the workspace root (packages/api/AGENTS.md), never buried deeper. A whole-repo run does not deep scan every workspace; write the repo root AGENTS.md (monorepo wide tooling, shared conventions) plus a light stub per workspace from its manifest, no code scan, with root pointers. The full conventions/gotchas/key files scan happens when the engineer runs /audit packages/api (Phase 3) or first builds there. A spot inside a workspace that warrants its own doc (packages/ui/src/mdx/) gets one in addition to the workspace root doc, linked from it. A doc already buried in a workspace with no workspace root doc: ask: "packages/ui has a context file at src/mdx/ but none at its root. Move it up to packages/ui/AGENTS.md, or keep it as a nested doc under a new packages/ui/AGENTS.md?" On move: relocate it to the workspace root. On keep nested: create the workspace root AGENTS.md AND keep the deep one, linked from root. Migrate legacy CLAUDE.md content per the convention above. Apply MONOREPO=yes plus the workspace list as you write.
Legacy migration (any phase): on ROOT_LEGACY, before proceeding ask permission: "I found a CLAUDE.md with project context but no AGENTS.md. I'll move its content into a new AGENTS.md (so all tools read it) and replace CLAUDE.md with a pointer. Proceed?" On yes: copy the content verbatim into AGENTS.md, then replace CLAUDE.md with the pointer; AGENTS.md now exists, so continue as Phase 4 (gap-fill). On no: leave both untouched and continue without migrating. Same for any nested <area>/CLAUDE.md.
Route to the selected phase
Phase 0 (ambiguous) is handled inline below. For Phases 1 to 4, read only the matching mode file, then follow it:
- Phase 1 (greenfield setup) →
modes/greenfield.md - Phase 2 (whole-repo scan) →
modes/whole-repo.md - Phase 3 (area scan) →
modes/area.md - Phase 4 (gap-fill) →
modes/gapfill.md
Do not read the other mode files. The greenfield and whole-repo modes additionally read modes/tool-skills.md for the Agent Skills / MCP sweep (skip it for area and gap-fill runs).
Phase 0: Classify (only when pre-flight is ambiguous)
Don't guess. Ask once via your agent's interactive option picker (AskUserQuestion on Claude Code), or plain text with the same options. Mark one option (recommended) by whichever signal is stronger (a scaffold like tree with a manifest but little history leans New; real feature code and deep history leans Existing), and the picker adds a free text custom slot last:
- question: "I can't tell if this is a new project or an existing codebase (<state why: e.g. 'a manifest exists but I see no source in a language I recognise', or 'files look like untouched scaffolding'>). Which is it?"
- header: "Project state"
- options: 1.
New project, "I'll ask for your coding standards and seed the context." → Phase 1 (read the manifest/scaffold for the stack; still ask standards). 2.Existing codebase, "I'll scan what's here and document it." → Phase 2.
After all phases
If no AGENTS.md was written when it should have been (the file is missing/empty), report the failure and do it again; don't relay success it didn't produce. Otherwise relay the report: what was discovered (2 to 4 bullets), what was written (file paths), what was proposed or skipped (if existing files were found).
Pattern presets
See patterns/ for the four coding style presets used in Phase 1 (greenfield mode).
Writing guide
See agent-prompt.md (the main thread reads it at write time; its per phase instructions and AGENTS.md templates).
© jsmastery-pro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 11 other files in skills/audit of jsmastery-pro/skills.
- SKILL.md
- agent-prompt.md
- agents/openai.yaml
- modes/area.md
- modes/gapfill.md
- modes/greenfield.md
- modes/tool-skills.md
- modes/whole-repo.md
- patterns/clean-architecture.md
- patterns/domain-driven.md
- patterns/functional.md
- patterns/solid-oop.md
Open the folder on GitHubat commit 43b69e4
Compare with similar skills
Project Context Auditor next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Project Context Auditor this skilljsmastery-pro/skills | 1.4k | — | ~3.2k | Automated safety check: Notes | MIT | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Dsh Web Documentationzhu1090093659/dsh-web | 8.5k | — | ~479 | Automated safety check: Pass | Apache-2.0 | |
| Claude Docs Consultantcentminmod/my-claude-code-setup | 2.7k | — | ~959 | Automated safety check: Pass | MIT | |
| Newprojectscunning1975/MixtapeTools | 470 | 1 repos | ~850 | Automated safety check: Pass | None | |
| Sync Public DocsCaldis/react-zmage | 946 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Dsh Web Documentation
zhu1090093659/dsh-web
A skill your agent uses when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
Claude Docs Consultant
centminmod/my-claude-code-setup
Consult official Claude Code documentation from code.claude.com using selective fetching.
Newproject
scunning1975/MixtapeTools
Scaffold a new research project with standard directory structure, CLAUDE.md template, and documented README.
Sync Public Docs
Caldis/react-zmage
A skill your agent uses when modifying public API in packages/core (types/global.ts, types/default.ts, index.ts, or package.json exports field), adding/renaming/removing props, changing default…
Review Docs
Kaggle/kaggle-environments
Audit a game environment's README.md and AGENTS.md against its engine implementation.
More from jsmastery-pro/skills
All 8 skills in this repoPre-Merge Check
jsmastery-pro/skills
A gate before merge: verify runs the real app against the spec, and review has a different model do a senior code review, without editing code.
Root Cause Debugging
jsmastery-pro/skills
Runs a reproduce, localize, hypothesize, test, fix and verify loop to find a bug's root cause, applies the minimal fix and hands off a regression test.
Develop Feature Builder
jsmastery-pro/skills
Builds a feature, page, component, API or data layer from an approved spec and AGENTS.md, and sends you back to /architect when a key decision is missing.
Change Documentation Writer
jsmastery-pro/skills
Writes PR descriptions, changelog entries, release notes and postmortems from the actual commits and diff, and saves each one in the right place.
Sync Project Knowledge
jsmastery-pro/skills
Runs as the last step after a completed change to keep AGENTS.md files, the project scope and linked spec status lines current, using only small surgical edits.
Living Product Scope Planner
jsmastery-pro/skills
Turns a product idea into a coarse, ordered scope kept in docs/scope, then keeps it current: plan a product, plan the next slice, enroll one feature or reconcile after shipping.
Related
Categories
Questions about Project Context Auditor
What does Project Context Auditor do?
Bootstraps a project's tool-agnostic AGENTS.md files for a greenfield project, an undocumented codebase or one area, adding only what is missing and never overwriting curated content. md plus nested area-specific files, judging what belongs globally versus locally; for a partially documented codebase, it compares existing docs with the code and adds only missing global facts or docs for undocumented areas, never clobbering curated content. It does not create specs, maintain files later or write feature scope; sibling skills own those jobs.
When should I use Project Context Auditor?
Project Context Auditor fits situations like: bootstrapping AGENTS.md files for a brand-new, unscaffolded project; backfilling documentation for an existing codebase that has none; filling documentation gaps in one area of a partially documented project.
How do I install Project Context Auditor in Claude Code?
Run `npx skills add jsmastery-pro/skills --skill audit -a claude-code`. Or copy the skill folder (skills/audit in jsmastery-pro/skills) into .claude/skills/audit in your project. Claude Code loads it when a task matches its description.
How do I install Project Context Auditor in Codex?
Run `npx skills add jsmastery-pro/skills --skill audit -a codex`. Or copy the skill folder (skills/audit in jsmastery-pro/skills) into .agents/skills/audit in your project. Codex loads it when a task matches its description.
Can I use Project Context Auditor in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jsmastery-pro/skills --skill audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit, .gemini/skills/audit, .github/skills/audit and .opencode/skills/audit in your project.
What does Project Context Auditor need to run?
Going by SKILL.md and its folder, Project Context Auditor needs the command-line tools its instructions call (git). Its frontmatter pre-approves these tools: Bash, Read, Grep, Glob, Write, Edit, Agent, AskUserQuestion.
Does Project Context Auditor access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Project Context Auditor safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Project Context Auditor use?
Project Context Auditor is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Project Context Auditor use?
About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Project Context Auditor?
Skills that share tags, products or a category with Project Context Auditor: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), Dsh Web Documentation (zhu1090093659/dsh-web, 8.5k stars), Claude Docs Consultant (centminmod/my-claude-code-setup, 2.7k stars) and Newproject (scunning1975/MixtapeTools, 470 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Project Context Auditor?
jsmastery-pro (a GitHub organization) maintains it in jsmastery-pro/skills, which has 1,443 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on August 9, 2026.
Source: jsmastery-pro/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.