plugins/edit-utils/skills/auto-config/SKILL.md
Auto-detect project formatting tools and configure edit-utils settings
npx skillsauth add nsheaps/ai-mktpl auto-configInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Detect the project's formatting and linting tools and write a plugins.settings.yaml override.
Explore the project for formatting configuration:
.prettierrc, .prettierrc.json, .prettierrc.yaml, prettier.config.*biome.json, biome.jsonc.editorconfigpyproject.toml (black, ruff)mise.toml (npm tools like prettier, eslint)package.json (scripts, devDependencies)Determine the formatter command:
formatter: "prettier --write"formatter: "biome format --write"formatter: "black" or formatter: "ruff format"Determine file extensions from the project's source files and formatter config.
Write the config to $CLAUDE_PROJECT_DIR/.claude/plugins.settings.yaml:
edit-utils:
enabled: true
formatter: "prettier --write"
extensions:
- .json
- .yaml
- .yml
- .md
- .ts
- .tsx
command -v) and test it on a sample file.This skill implements the auto-config pattern: instead of hardcoding tool assumptions, the plugin discovers what tools the project uses and configures itself accordingly. This makes the plugin work across diverse projects without manual setup.
For session-start automation, a SessionStart hook can invoke this skill using a fast model (haiku) to explore the project and populate the config on first use.
tools
Manually reproduce what the github-app plugin's SessionStart hook does to make a GitHub App installation token usable in the current session — materialize the PEM, generate the token, isolate GH_CONFIG_DIR, write the runtime env file, and wire CLAUDE_ENV_FILE so every Bash call sees GH_TOKEN/GITHUB_TOKEN. Use when the hook did not run, the token is missing from the environment, or a shell/teammate needs the token wired up by hand. <example>GH_TOKEN isn't set even though github-app is configured</example> <example>the github-app SessionStart hook didn't run, set up the token manually</example> <example>wire the github app token into CLAUDE_ENV_FILE</example> <example>gh keeps falling back to the wrong account, isolate GH_CONFIG_DIR</example>
tools
Manually configure the GitHub App bot git identity the way the github-app plugin's SessionStart hook does — resolve the app slug and bot user ID, build the <slug>[bot] name and noreply email, set GIT_AUTHOR_*/GIT_COMMITTER_* env vars, and write an isolated GIT_CONFIG_GLOBAL with the gh auth git-credential helper. Use when commits are attributed to the wrong account, "Author identity unknown" appears, or git identity must be set up by hand. <example>my commits are showing up as the handler, not the bot</example> <example>git says Author identity unknown after the github-app hook ran</example> <example>configure the github app bot git identity manually</example> <example>set up the gh credential helper for git push</example>
tools
Manages spec files for requirements capture and validation
tools
# Bash Chaining Alternatives This skill teaches you how to work around the bash command chaining restriction enforced by this plugin. ## Why Chaining is Blocked The `bash-command-rejection` plugin blocks these operators: | Operator | Name | Why Blocked | | -------- | ---------- | ----------------------------------------------------------------------------------- | | `&&` | AND chain | Runs cmd2 only if cmd1 su