agentleFS
YulivuYulivu/debuffer-skills/skills/skills-codex/research-pipeline/SKILL.md

research-pipeline

Skill9 starsChanged 3 months agoMITView on GitHub

Lightweight AutoDL-first research pipeline: idea discovery → blueprint → experiment planning/AutoDL readiness checks → prompt-only review/audit → optional evidence-checked paper planning. Adapts to venue-only, reference-paper/codebase, idea-doc, existing-repo, or partial-results starts; avoids heavy local compute, defaults to concise artifacts, and prepares AutoDL/HPC approval-bounded runs. Use when user says \"全流程\", \"full pipeline\", \"从找idea到投稿\", \"end-to-end research\", or wants a complete but user-gated research lifecycle. Manuscript drafting is allowed only after formal runs and evidence audit pass.

16 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use invention-structuring, jurisdiction-format and 7 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.
  • raja21068Skill

    invention-structuring

    Structure a raw invention idea into a formal invention disclosure. Use when user says \"构建发明\", \"structure invention\", \"发明构建\", \"invention disclosure\", or wants to formalize a rough idea into a patent-ready structure.

    Also in 3 projects that use this

  • raja21068Skill

    jurisdiction-format

    Compile patent application into jurisdiction-specific filing format. Use when user says \"格式转换\", \"jurisdiction format\", \"国家格式\", \"compile patent\", or wants formatted patent documents for CN/US/EP filing.

    Also in 3 projects that use this

  • rongaredeSkill

    semantic-scholar

    使用 Semantic Scholar API 检索和验证学术论文。支持并发多关键词搜索、批量 ID/DOI 查询、引用分析、批量补全摘要、统一 Markdown 导出。覆盖 2.14 亿+ 学术论文,无需 API Key 即可使用。触发词:论文检索、论文验证、Semantic Scholar、S2 搜索、查论文、补全摘要、导出MD

    Also in 5 projects that use this

  • +6 more from raja21068

The file

Show its rules and text

We split this skill into the rules it gives an agent

28 rules. 0 are common, 10 are distinctive, and 18 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 18

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read ../shared-references/lightweight-research-pack.md before running the pipeline.

    line 23
  2. Very specific:

    BLUEPRINT_GATE = required at handoffs: before formal experiment planning, AutoDL formal runs, or paper planning, create or refresh …

    line 50
  3. Distinctive:

    Keep routine updates compact.

    line 54
  4. Very specific:

    OVERNIGHT_HEARTBEAT = false: when explicitly enabled, only checks external machine-readable progress and resumes a stalled phase.

    line 55
  5. Very specific:

    Read ../shared-references/project-guide-protocol.md when the user wants a project-wide guide or when crossing a stage gate.

    line 63
  6. Distinctive:

    Do not wrap an automatic reviewer loop in an external timer.

    line 120
  7. Very specific:

    If docs/project/RESEARCH_BRIEF.md exists, load it as detailed context (replaces one-line prompt).

    line 132
  8. Very specific:

    After idea-stage/IDEA_REPORT.md is generated, pause and present the top ideas to the user:

    line 148
  9. Very specific:

    If AUTO_PROCEED=false: Wait for user confirmation before continuing.

    line 160
  10. Very specific:

    When the user commits to an idea or stable method, run /research-blueprint before implementation or formal experiment planning.

    line 172
  11. Very specific:

    Wait for /experiment-bridge to complete and report its handoff summary before proceeding.

    line 211
  12. Distinctive:

    After the auto-review loop completes, run an evidence-readiness gate before any paper handoff.

    line 231
  13. Distinctive:

    Step 1: Write or update the compact research status:

    line 234
  14. Distinctive:

    Step 2: Check the manuscript-entry prerequisites:

    line 240
  15. Very specific:

    If any prerequisite fails, stop in the experiment/audit phase.

    line 248
  16. Very specific:

    If the gate passes, generate docs/paper/NARRATIVE_REPORT.md as a compact evidence-audited handoff for paper-plan, not as a manuscript draft.

    line 253
  17. Distinctive:

    If Stage 4 does not pass, skip this stage entirely.

    line 296
  18. Very specific:

    If Stage 4 passes and AUTO_WRITE=false (default), stop after presenting the paper-planning command, not a manuscript command:

    line 298
  19. Very specific:

    If AUTO_WRITE=true, first run or request /paper-plan.

    line 306
  20. Very specific:

    If VENUE is missing, stop and ask.

    line 312
  21. Very specific:

    If formal evidence or the paper plan readiness check is missing, stop and write docs/project/NEXT_ACTIONS.md.

    line 313
  22. Distinctive:

    If manual figures are required, pause and list them.

    line 315
  23. Very specific:

    Only after Stage 4 finalizes an evidence-audited docs/paper/NARRATIVE_REPORT.md, optionally invoke /render-html on the narrative report:

    line 319
  24. Very specific:

    Non-blocking: if /render-html fails (helper missing, file write error, etc.), log the failure and continue.

    line 331
  25. Very specific:

    Large file handling: If the Write tool fails due to file size, immediately retry using Bash (cat << 'EOF' > file) to write in chunks.

    line 346
  26. Distinctive:

    Documentation: Every stage updates its own output file.

    line 352
  27. Distinctive:

    Fail gracefully: If any stage fails (no good ideas, experiments crash, review loop stuck), report clearly and suggest alternatives rather …

    line 353
  28. Distinctive:

    Sweet spot: Run Stage 1 in the evening, launch Stage 2-3 before bed, wake up to a reviewed paper.

    line 363

“Common” is measured: kept by at least 6 in 10 of the 13 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

Full Research Pipeline: Idea → Experiments → Submission

Capability Routing

This is a first-layer entry skill. Keep it loaded as the user-facing route; when a request needs a specialized capability below, resolve the debuffer repo root from .debuffer_skills/installed-skills-codex.txt (repo_root) when available, read the referenced library SKILL.md, then follow that skill. Do not copy the whole library skill into this file.

  • /research-refine: read ../../skills-codex-library/idea-method/research-refine/SKILL.md.
  • /experiment-queue: read ../../skills-codex-library/experiments/experiment-queue/SKILL.md.
  • /auto-review-loop: read ../../skills-codex-library/review/auto-review-loop/SKILL.md.
  • /dse-loop: read ../../skills-codex-library/workflow/dse-loop/SKILL.md.
  • /meta-optimize: read ../../skills-codex-library/workflow/meta-optimize/SKILL.md.

End-to-end autonomous research workflow for: $ARGUMENTS

Customized Pack Defaults

Read ../shared-references/lightweight-research-pack.md before running the pipeline. In this customized pack, the following defaults override older autonomous settings below unless the user explicitly asks for legacy automation:

  • STARTUP_MODE = auto: classify the project as venue-only, reference-paper, reference-codebase, idea-doc, existing-repo, or partial-results before choosing the first stage.
  • AUTO_PROCEED = false, HUMAN_CHECKPOINT = true, COMPACT = true, RENDER_HTML = false.
  • REVIEW_MODE = prompt-only: generate review-prompts/*_review_prompt.md and wait for pasted feedback from a separate review conversation. Do not call reviewer agents unless the user explicitly opts into legacy review.
  • AUTONOMOUS_REVIEW = false: automatic reviewer loops are available only after explicit user authorization for the current run. Preserve raw reviews and append-only obligations.
  • CODE_REVIEW = prompt-only: for implementation review, write a code-review prompt file instead of calling a reviewer agent directly.
  • LOCAL_HEAVY_COMPUTE = false, DEPLOY_TARGET = autodl: local work is limited to edits, lint/tests, dry runs, and tiny smoke checks. Heavy training or sweeps must be prepared through /autodl-hpc with approval gates.
  • AUTO_WRITE = false remains the default and cannot override the evidence gate. Produce compact docs/project/PROJECT_BRIEF.md, docs/evidence/findings.md, docs/experiments/EXPERIMENT_LOG.md, and docs/project/NEXT_ACTIONS.md; create docs/paper/NARRATIVE_REPORT.md only after formal runs and evidence audit pass, or when the user explicitly asks for a clearly labeled pre-paper gap artifact.
  • BLUEPRINT_GATE = required at handoffs: before formal experiment planning, AutoDL formal runs, or paper planning, create or refresh docs/project/RESEARCH_BLUEPRINT.md and docs/project/BLUEPRINT_GATE.md via /research-blueprint. Keep routine updates compact.
  • OVERNIGHT_HEARTBEAT = false: when explicitly enabled, only checks external machine-readable progress and resumes a stalled phase. It never accepts a quality verdict, changes scope, or bypasses a user gate.

For venue-specific review and writing, read ../shared-references/venue-profiles.md and apply the target venue profile (ICLR, AAAI, JMLR, TPAMI, NeurIPS/ICML, or IEEE).

Read ../shared-references/project-guide-protocol.md when the user wants a project-wide guide or when crossing a stage gate. Keep PROJECT_STATUS.md updated after each accepted stage. Generate docs/project/PROJECT_GUIDE.md, docs/project/RESEARCH_BLUEPRINT.md, docs/project/BLUEPRINT_GATE.md, docs/experiments/EXPERIMENT_PROTOCOL.md, docs/evidence/EVIDENCE_LEDGER.md, or docs/paper/PAPER_GUIDE.md only when their gate conditions are met; otherwise update compact memory files.

Constants

  • AUTO_PROCEED = false — Wait for explicit user confirmation before leaving idea selection or any expensive gate.
  • ARXIV_DOWNLOAD = false — When true, /research-lit downloads the top relevant arXiv PDFs during literature survey. When false (default), only fetches metadata via arXiv API. Passed through to /idea-discovery → /research-lit.
  • HUMAN_CHECKPOINT = true — Pause review loops after each round so the user can inspect feedback before fixes or new experiments.
  • REVIEWER_DIFFICULTY = medium — Controls the requested review depth. In the default prompt-only mode, it changes the generated review checklist. hard adds Reviewer Memory and Debate Protocol when an automatic reviewer backend is explicitly authorized; nightmare adds direct repository-reading verification under the same authorization. These settings never select a model or backend by themselves. Passed through to /auto-review-loop.
  • CODE_REVIEW = prompt-only — Write a code-review prompt before deployment. An automatic reviewer backend requires explicit authorization for the current run and must follow shared-references/model-policy.md.
  • BASE_REPO = false — GitHub repo URL to use as base codebase. When set, /experiment-bridge clones the repo first and implements experiments on top of it. When false (default), writes code from scratch or reuses existing project files. Passed through to /experiment-bridge.
  • COMPACT = true — Generate compact summary files for short-context models and session recovery. Passed through to /idea-discovery and /experiment-bridge.
  • AUTO_WRITE = false — When true, it may request the paper-writing workflow only after formal runs, evidence audit, and paper-plan gates pass. When false (default), stop at the next allowed gate and do not present manuscript commands.
  • VENUE = ICLR — Target venue for paper writing (Stage 5). Only used when AUTO_WRITE=true. Options: ICLR, NeurIPS, ICML, CVPR, ACL, AAAI, ACM, IEEE_CONF, IEEE_JOURNAL.
  • RENDER_HTML = false — Render docs/paper/NARRATIVE_REPORT.md only when that evidence-audited artifact is actually generated and the user asks or opts in.

💡 Override via argument, e.g., /research-pipeline "topic" — AUTO_PROCEED: false, human checkpoint: true, difficulty: nightmare, code review: false, base repo: https://github.com/org/project, auto_write: true, venue: NeurIPS.

Overview

This skill chains the research lifecycle into a gated pipeline:

/idea-discovery → /research-blueprint → /experiment-bridge/autodl-hpc → /experiment-audit → /paper-plan → /paper-writing (gated)
├── Workflow 1 ──┤├── Stage-gate design ──┤├── Workflow 1.5 ──┤├── Workflow 2 ───┤├── Workflow 3 ──┤

It orchestrates the major research workflows plus blueprint and evidence readiness checks. Paper writing is optional and controlled by both AUTO_WRITE and the manuscript entry check; AUTO_WRITE=true is ignored when formal evidence is missing.

Strong Loop Hygiene

For unattended idea/search/experiment loops, use the cheap deterministic helpers:

  • tools/iteration_log.py note <root> <run_id> <phase> <new_findings> after each iteration. Consecutive zero-finding rounds force a structural pivot at 2 and human attention at 4. The signal changes direction only; it never judges whether a result is good enough.
  • tools/watchdog.py --register '{"name":"<run>","type":"loop","state_file":"<path>","stale_after_seconds":21600}' for long loops that rewrite a JSON state file. STALE/MISSING is detect-only: surface it and resume/pivot explicitly; do not let the watchdog restart or accept verdict-bearing work.

Do not wrap an automatic reviewer loop in an external timer. Use its internal round state and integrity audit. External cadence is reserved for job completion, resource availability, artifact arrival, or scheduled literature changes.

An explicitly enabled overnight heartbeat may read state, inspect external machine-verifiable facts, resume a stalled phase without changing its contract, record the wake event, and stop. It may say "keep going", never "good enough".

Pipeline

Stage 1: Idea Discovery (Workflow 1)

If docs/project/RESEARCH_BRIEF.md exists, load it as detailed context (replaces one-line prompt). Fall back to legacy root RESEARCH_BRIEF.md only for older projects. See templates/RESEARCH_BRIEF_TEMPLATE.md.

Invoke the idea discovery pipeline:

/idea-discovery "$ARGUMENTS"

This internally runs: /research-lit → /idea-creator → /novelty-check → /research-review

Output: idea-stage/IDEA_REPORT.md with ranked, validated, pilot-tested ideas.

Review Tracing follows the downstream review skills. Stage 1 and Stage 3 preserve reviewer prompts/responses through their own trace protocols so the final handoff can be audited.

🚦 Gate 1 — Human Checkpoint:

After idea-stage/IDEA_REPORT.md is generated, pause and present the top ideas to the user:

📋 Idea Discovery complete. Top ideas:

1. [Idea 1 title] — Pilot: POSITIVE (+X%), Novelty: CONFIRMED
2. [Idea 2 title] — Pilot: WEAK POSITIVE (+Y%), Novelty: CONFIRMED
3. [Idea 3 title] — Pilot: NEGATIVE, eliminated

Recommended: Idea 1. Shall I proceed with implementation?

If AUTO_PROCEED=false: Wait for user confirmation before continuing. The user may:

  • Approve the idea → proceed to Stage 2. /experiment-bridge reads refine-logs/EXPERIMENT_PLAN.md already generated by /idea-discovery.
  • Request changes (e.g., "combine Idea 1 and 3", "focus more on X") → update the idea prompt with user feedback, re-run /idea-discovery with refined constraints, and present again.
  • Reject all ideas → collect feedback on what's missing, re-run Stage 1 with adjusted research direction. Repeat until the user commits to an idea.
  • Stop here → save current state to idea-stage/IDEA_REPORT.md for future reference.

If AUTO_PROCEED=true: Present the top ideas, wait 10 seconds for user input. If no response, auto-select the #1 ranked idea (highest pilot signal + novelty confirmed) and proceed to Stage 2. Log: "AUTO_PROCEED: selected Idea 1 — [title]".

⚠️ This gate waits for user confirmation when AUTO_PROCEED=false. When true, it auto-proceeds after presenting results. The rest of the pipeline (Stages 2-3) is expensive (GPU time + multiple review rounds), so set AUTO_PROCEED=false if you want a final review checkpoint before committing GPU resources.

Stage 1.5: Research Blueprint Gate

When the user commits to an idea or stable method, run /research-blueprint before implementation or formal experiment planning. It writes docs/project/RESEARCH_BLUEPRINT.md with the sequential overall progress table and docs/project/BLUEPRINT_GATE.md with PASS / CONDITIONAL / BLOCKED. Continue only to the allowed next step recorded in the gate. If the idea is still exploratory, keep using docs/project/PROJECT_BRIEF.md, PROJECT_STATUS.md, and docs/project/NEXT_ACTIONS.md instead of creating the large blueprint.

Stage 2: Experiment Bridge (Workflow 1.5)

Once the user confirms which idea to pursue, delegate implementation and deployment to /experiment-bridge:

/experiment-bridge "$CHOSEN_IDEA_TITLE" — code review: $CODE_REVIEW, base repo: $BASE_REPO, compact: $COMPACT

💡 Queue routing is automatic: /experiment-bridge Phase 4 routes each milestone by job count — ≤5 jobs → /run-experiment, ≥10 jobs or teacher→student phase dependencies → /experiment-queue (with OOM retry, wave gating, crash-safe state). No manual override is needed.

What this does (fully autonomous):

  1. Parses refine-logs/EXPERIMENT_PLAN.md — extracts milestones, run order, compute budget
  2. Implements experiment code — extends pilot to full scale, follows existing codebase conventions
  3. Code-review handoff — writes a prompt-only review request for logic bugs, incorrect metrics, and ground-truth misuse before any GPU time is spent; automatic review is opt-in
  4. Sanity check — runs the smallest experiment first to verify the environment; auto-debugs failures (up to 3 attempts, with /codex:rescue fallback)
  5. Deploys full experiments — auto-routes by job count (≤5 → /run-experiment, ≥10 → /experiment-queue with OOM retry, wave gating, crash-safe state)
  6. Collects initial results — parses outputs, updates refine-logs/EXPERIMENT_TRACKER.md, runs /training-check if W&B is configured
  7. Auto-plans ablations via /ablation-planner if main results are positive

Output:

  • refine-logs/EXPERIMENT_RESULTS.md — structured results by milestone
  • refine-logs/EXPERIMENT_TRACKER.md — updated run-by-run status
  • docs/experiments/EXPERIMENT_LOG.md (when COMPACT=true) — session-recovery-friendly log

Monitor progress (while experiments run):

/monitor-experiment [server]

Wait for /experiment-bridge to complete and report its handoff summary before proceeding.

Stage 3: Auto Review Loop (Workflow 2)

Once initial results are in, start the autonomous improvement loop:

/auto-review-loop "$ARGUMENTS — [chosen idea title], difficulty: $REVIEWER_DIFFICULTY"

What this does (up to 4 rounds):

  1. The configured review mode evaluates the work (score, weaknesses, minimum fixes); prompt-only mode records the request and waits for pasted feedback
  2. Claude Code implements fixes (code changes, new experiments, reframing)
  3. Deploy fixes, collect new results
  4. Re-review → repeat until score ≥ 6/10 or 4 rounds reached

Output: review-stage/AUTO_REVIEW.md with full review history and final assessment.

Stage 4: Evidence Summary & Paper-Readiness Gate

After the auto-review loop completes, run an evidence-readiness gate before any paper handoff.

Step 1: Write or update the compact research status:

  • PROJECT_STATUS.md
  • docs/evidence/findings.md
  • docs/experiments/EXPERIMENT_LOG.md
  • docs/project/NEXT_ACTIONS.md

Step 2: Check the manuscript-entry prerequisites:

  • formal baseline/main/required ablation runs exist for paper-level findings;
  • raw evidence names run folders, metrics, configs/resolved configs, seeds, logs/metadata, and result summaries;
  • docs/evidence/EVIDENCE_LEDGER.md, CLAIMS_FROM_RESULTS.md, or an equivalent audit maps findings to raw evidence and unresolved gaps;
  • docs/project/BLUEPRINT_GATE.md does not block paper planning.

If any prerequisite fails, stop in the experiment/audit phase. Do not generate docs/paper/NARRATIVE_REPORT.md, do not render HTML, and do not present /paper-writing. The next step should be experiment-plan, autodl-hpc, experiment-audit, evidence-ledger completion, or stop.

If the gate passes, generate docs/paper/NARRATIVE_REPORT.md as a compact evidence-audited handoff for paper-plan, not as a manuscript draft.

The narrative report must contain:

  • Problem statement and core finding
  • Method summary
  • Formal quantitative results with raw evidence for each finding
  • Figure/table inventory (which exist, which need manual creation)
  • Limitations and remaining follow-up items

Output: compact status files, and docs/paper/NARRATIVE_REPORT.md only when the evidence readiness check passes.

# Research Pipeline Report

**Direction**: $ARGUMENTS
**Chosen Idea**: [title]
**Date**: [start] → [end]
**Pipeline**: idea-discovery → experiment-bridge → auto-review-loop

## Journey Summary
- Ideas generated: X → filtered to Y → piloted Z → chose 1
- Implementation: [brief description of what was built]
- Experiments: [number of GPU experiments, total compute time]
- Review rounds: N/4, final score: X/10

## Paper-Readiness Gate
- Formal runs complete: [yes/no + evidence path]
- Evidence audit complete: [yes/no + artifact path]
- Allowed next step: [experiment-plan/autodl-hpc/experiment-audit/paper-plan/stop]
- Narrative report: [generated only if readiness check passed]

## Remaining TODOs (if any)
- [items flagged by reviewer that weren't addressed]

Stage 5: Paper Planning / Writing (Gated Optional)

This corresponds to Stage 6: Paper Writing in the macro lifecycle, but that stage remains closed until formal runs, evidence audit, and paper-plan gates pass.

If Stage 4 does not pass, skip this stage entirely.

If Stage 4 passes and AUTO_WRITE=false (default), stop after presenting the paper-planning command, not a manuscript command:

evidence readiness check passed. Next allowed step:
/paper-plan "docs/paper/NARRATIVE_REPORT.md" --venue [VENUE]

If AUTO_WRITE=true, first run or request /paper-plan. Invoke /paper-writing only if the resulting docs/paper/PAPER_PLAN.md says the manuscript entry check passed and the user explicitly confirms. Never proceed from Stage 4 directly to LaTeX drafting.

Checks before any manuscript drafting:

  • If VENUE is missing, stop and ask. Do not silently use a default venue.
  • If formal evidence or the paper plan readiness check is missing, stop and write docs/project/NEXT_ACTIONS.md.
  • If manual figures are required, pause and list them. Wait for user approval.

Render HTML view (opt-in, only after evidence readiness check passes)

Only after Stage 4 finalizes an evidence-audited docs/paper/NARRATIVE_REPORT.md, optionally invoke /render-html on the narrative report:

/render-html "docs/paper/NARRATIVE_REPORT.md" --no-review

--no-review is intentional: this is an internal handoff doc, not a reviewer-facing final artifact. Output: NARRATIVE_REPORT.html next to the MD, with embedded source SHA256.

Non-blocking: if /render-html fails (helper missing, file write error, etc.), log the failure and continue. The HTML view is a convenience artifact, not a paper-readiness prerequisite.

Skip this step if RENDER_HTML = false.

Output Protocols

Follow these shared protocols for all output files:

  • Output Versioning Protocol — write timestamped file first, then copy to fixed name
  • Output Manifest Protocol — log every output to docs/project/OUTPUT_MANIFEST.md
  • Output Language Protocol — respect the project's language setting

Key Rules

  • Large file handling: If the Write tool fails due to file size, immediately retry using Bash (cat << 'EOF' > file) to write in chunks. Do NOT ask the user for permission — just do it silently.
  • Human checkpoint after Stage 1 is controlled by AUTO_PROCEED. When false, do not proceed without user confirmation. When true, auto-select the top idea after presenting results.
  • Stages 2-3 can run autonomously once the user confirms the idea. This is the "sleep and wake up to results" part.
  • If Stage 3 ends at round 4 without positive assessment, stop and report remaining issues. Do not loop forever.
  • Budget awareness: Track total GPU-hours across the pipeline. Flag if approaching user-defined limits.
  • Documentation: Every stage updates its own output file. The full history should be self-contained.
  • Fail gracefully: If any stage fails (no good ideas, experiments crash, review loop stuck), report clearly and suggest alternatives rather than forcing forward.

Typical Timeline

StageDurationCan sleep?
1. Idea Discovery30-60 minYes if AUTO_PROCEED=true
2. Experiment Bridge30-120 min (implement + review + deploy + collect)Yes ✅
3. Auto Review1-4 hours (depends on experiments)Yes ✅

Sweet spot: Run Stage 1 in the evening, launch Stage 2-3 before bed, wake up to a reviewed paper.

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.