agentleFS
UlyssesLeoLeeUlyssesLeoLee/MAGOS/skills/git-recon/SKILL.md

git-recon

Skill1 starsChanged 8 days agoApache-2.0View on GitHub

查看仓库状态(只读);/git-recon [--remote] [--help].

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. Smirnov-Labs/claude-skills★ 6same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Default: Read-only snapshot using existing local refs.

    line 22
  2. Very specific:

    Do not use commands/*.md for this adapter.

    line 48
  3. Very specific:

    If a shared file cannot be read, name the missing path, report that the MAGOS installation is incomplete, and continue read-only with the …

    line 50

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

GitRecon

Command adapter for the canonical /GitRecon command of the MAGOS (Multi-Agent Git Orchestrator) package. Use it when the user explicitly invokes /git-recon in Hermes or $git-recon in Codex.

Usage

  • Hermes: /git-recon [--remote] [--lang <language>] [--help]
  • Codex: $git-recon [--remote] [--lang <language>] [--help]
  • --remote: Refresh remote-tracking refs before classifying the repository; it does not change branches, worktrees, or commit history.
  • --lang <language>: Language of the reply, as a name or code (for example English, ja); Chinese when absent. Command names, options, branch names, paths, SHAs, and status codes stay untranslated.
  • --help: Show this inline usage and argument description, then stop without inspecting the repository.
  • Default: Read-only snapshot using existing local refs; no remote refresh.

Examples: /git-recon --remote, $git-recon --remote, $git-recon --lang English, $git-recon --help.

Arguments

  • Codex: the arguments are the text that follows $git-recon in the user's message.
  • Plugin installs prefix the name with the plugin name: /magos:git-recon in Hermes, $magos:git-recon in Codex; Claude Code hides this adapter and offers the command /magos:GitRecon instead. The arguments follow the name the same way.
  • Hermes: the arguments are the instruction Hermes appends after the skill content, introduced by "The user has provided the following instruction alongside the skill invocation:" (single command) or User instruction: (stacked commands). An empty instruction means no arguments.

If --help is present, even with other arguments, answer from the inline Usage section above and stop before any tool call, file read, or repository inspection. For an unknown option, explain the error, show the same help, and stop. Read the shared files below only for a normal invocation.

Shared files

This adapter belongs to the MAGOS package. The shared files are in the package root, two directories above this skill's directory:

  1. ../../SKILL.md: shared orchestration rules and safety invariants.
  2. ../../references/commands.md section 1. GitRecon: command contract and output format.
  3. ../../references/reconnaissance.md: repository inspection steps.

Locate them as follows:

  • Codex: resolve the paths relative to the directory that contains this SKILL.md.
  • Hermes: take the absolute path from the [Skill directory: ...] line (when the skill was loaded with skill_view instead of a slash command, from the skill_dir field it returns), go up two directories, and read the files with the file or terminal tool. The skill viewer rejects paths that contain ... Alternatively, load the skill multi-agent-git-orchestrator (magos:git-orchestrator under a Hermes plugin install) and view its references/commands.md and references/reconnaissance.md files.
  • Other hosts: resolve the paths relative to this file.

Do not use commands/*.md for this adapter. Those files are Claude Code slash-command wrappers with Claude-specific loading steps.

If a shared file cannot be read, name the missing path, report that the MAGOS installation is incomplete, and continue read-only with the safety defaults below.

Execution

Execute the canonical /GitRecon command with the supplied arguments. Inspect the current repository before reporting state-dependent findings. Default to read-only; --remote only permits refreshing remote-tracking refs. Never change branches, worktrees, or commit history. Reply in the language selected by --lang (Chinese when absent); never translate commands, options, branch names, paths, SHAs, or status codes. Remove --lang and its value from the arguments before parsing the rest.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.