agentleFS
Sign inStart free
pablocaegpablocaeg/claude-army/skills/challenge/SKILL.md

challenge

Skill2 starsChanged 8 months agoMITView on GitHub

Run the challenger agent against your current changes to simulate the lead reviewer's feedback before submitting. Requires a forge analysis with reviewer patterns.

33 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use prove-it, ingest and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Neko-Catpital-LabsSkill

    prove-it

    Shared evidence rule for investigating, diagnosing, debugging, proving, or explaining what happened or why for any problem or situation: do not assert something is fixed, working, passing, merged, or running unless you personally observed it this turn and can show what you saw; do not assert it was caused by X until a repro and controlled isolation prove that cause.

    Also in 3 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 4 projects that use this

  • MetaSkill

    roadmap

    Build, continue, inspect, or visualize a source-grounded mathematical roadmap and theorem DAG in an existing Autoform Markdown blueprint. Use for source research, repository-wide inventories of existing and planned mathematics, scope, coverage, milestones, and roadmap articles; do not create repository infrastructure or prove Lean declarations.

    Also in 3 projects that use this

  • GoogleSkill

    critique

    Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.

    Also in 3 projects that use this

  • genomewalkerSkill

    learn

    Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.

    Also in 4 projects that use this

  • AnthropicSkill

    start

    Set up your bio-research environment and explore available tools. Use when first getting oriented with the plugin, checking which literature, drug-discovery, or visualization MCP servers are connected, or surveying available analysis skills before starting a new project.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 2

    Distinctive

    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. Very specific:

    Read .context/forge-analysis.md for reviewer patterns

    line 11
  2. Very specific:

    If it doesn't exist, tell the user to run /claude-army:analyze first

    line 12
  3. Distinctive:

    Run git status and git diff --name-only to find all changes

    line 16
  4. Distinctive:

    Read every changed/new file

    line 17

“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “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

Simulate the lead reviewer's feedback on the current changes. Uses reviewer patterns from the forge analysis.

Before Starting

  1. Read .context/forge-analysis.md for reviewer patterns
  2. If it doesn't exist, tell the user to run /claude-army:analyze first

Process

  1. Run git status and git diff --name-only to find all changes
  2. Read every changed/new file
  3. Apply reviewer checks in tier order (Tier 1 first, most likely to be raised)
  4. For factual claims (thresholds, tax classification, etc.): WebSearch to verify
  5. For source URLs: WebFetch to confirm accessibility

Output

Present findings as the lead reviewer would — questions, not demands:

## Review Simulation: [Reviewer Name]

### Questions (likely to ask)
**file:line** — [question in their voice]
Fix with: [which agent or direct edit]

### Issues (would flag)
**file:line** — [what's wrong]
Fix with: [which agent]

### What Looks Good
[acknowledge well-done parts]

### Fix Plan
| # | Issue | Fix Agent | Instruction |
|---|-------|-----------|-------------|
| 1 | ... | ... | ... |

Execution order: [dependencies]

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.

Check your setup, free