Profile My skills Saved My plugins Edit profile Submit a skill

← all publishers

Londopy

@londopy source repo

4 published skills

  1. ▌
    Git Attribution · londopy bundle
    Find and remove AI co-author attribution from a git repo - the Co-Authored-By trailer and "Generated with" footer that Claude Code, Codex, Copilot, Cursor, Gemini and others add to commits and that put the agent in your GitHub contributor graph. Works from any agent. Use this whenever the user says Claude, Codex or an AI showed up as a contributor, asks to remove Co-Authored-By or stop adding it, asks whether commits are still being attributed to an agent, wants AI attribution scrubbed from history, wants a repo checked for AI co-authors before pushing or publishing, or asks to block pushes that carry the trailer. Also use it before you push to a repo where the user has said they want no AI attribution.
    0 installs
  2. ▌
    Settings Effective · londopy bundle
    Show the merged Claude Code settings actually in effect and which file decided each key - managed policy, --settings, .claude/settings.local.json, .claude/settings.json, ~/.claude/settings.json and ~/.claude.json - and name the reasons a setting is not applying. Runs from any agent; it inspects Claude Code's files. Use this whenever the user says a Claude Code setting isn't working or isn't taking effect, asks why they are still being prompted for a tool they allowed, asks which settings file wins or where a value is coming from, asks what a settings key does or where it goes, wants their settings files checked for typos or keys in the wrong file, asks whether a project is trusted, or wants to see all their hooks, permission rules or env in one place. Also use it after you edit any settings.json yourself, to confirm the key landed where it applies.
    0 installs
  3. ▌
    MCP Rollcall · londopy bundle
    Take a roll call of configured MCP servers - which are configured where, which will fail to connect and exactly why (missing command, dead path, unset variable, nothing listening on the port, the server's own stderr), and what each one costs in tools and context. Reads Claude Code, Codex, Cursor, Gemini CLI, Copilot CLI, VS Code, Windsurf and OpenCode config files. Use this whenever the user says an MCP server failed to connect, shows "Connection closed" or "still connecting", asks why a server or its tools are missing, asks what MCP servers they have or where one is configured, asks which servers are slow or heavy, wants MCP config checked before committing a .mcp.json, config.toml or mcp.json, asks which agent a server is configured for, or after adding or editing a server. Also use it when your own system context lists a server as failed and the user asks about it.
    0 installs
  4. ▌
    Skill Rollcall · londopy bundle
    Take a roll call of installed skills - see which are registered, which are new, which will never register and why, and fix or load them without restarting. Works in Claude Code, Codex, Cursor, Gemini CLI, Copilot, OpenCode and any other Agent Skills host. Use this whenever the user says reload skills, refresh skills, rescan skills, re-index skills, roll call, lint my skills, audit my skills, "I just installed a skill", "I just added/edited a SKILL.md", asks whether you can see a particular skill, asks why a skill is not showing up or not triggering, asks how much context their skills cost, asks which skills another agent can see, or wants a skills repo checked before publishing. Also use it after you yourself install or write a skill mid-session, to confirm it registered.
    0 installs