agentleFS
AIimaginedAIimagined/Godmode/skills/godmode-research/SKILL.md

godmode-research

Skill6 starsChanged 3 months agoApache-2.0View on GitHub

Study an outside source repository in a fixed order - licence, tree, the two or three implementing source files, line-cited receipts - and record both an import verdict and a behaviour verdict, refusing adopt or extend on a surface-only reading. Use when an outside codebase is being surveyed for a mechanism worth borrowing. Not for rebuilding that mechanism under Godmode names, and not for root-causing a failure in this repository.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read PURPOSE.md for the archive records this skill exists to close.

    line 40
  2. Distinctive:

    Never record adopt or extend from a README, doc or release-note reading.

    line 44
  3. Distinctive:

    Never study a source's code before its licence is classified in step 1.

    line 45
  4. Very specific:

    Never name the studied source in shipped text (code, docs, skills, changelog).

    line 46
  5. Very specific:

    Never copy source text into this repository.

    line 47
  6. Very specific:

    Never skip the receipt for a file that the verdict relies on.

    line 48
  7. Very specific:

    Every absorb: decision carries both verdicts and at least one receipt naming a source file.

    line 53
  8. Distinctive:

    If an assertion cannot be proved, report the unmet assertion and the next safe action rather than the outcome it was meant to prove.

    line 55

≈ “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

Godmode Research

Outcome

An outside source is judged on what was actually opened, not on its landing page: every file read carries a receipt with its line range and a digest of the slice, the licence is classified before anything else, and the recorded verdict pair (import and behaviour) is refused as adopt or extend unless a receipt names a source file rather than a README, a doc or a release note.

Use

  • An outside repository is being surveyed for a mechanism this project might borrow.
  • An earlier survey recorded a verdict and its reading depth is in doubt.
  • A source's licence has to be classified before any of it is studied closely.
  • A survey needs to show, per source, how many files were opened and whether it stayed on the surface.

Do Not Use

  • Rebuilding a studied mechanism in stdlib under Godmode names and pinning it with a reproducing test - that is godmode-replicate.
  • Root-causing a failure inside this repository - that is godmode-investigation.
  • Independently rechecking a verdict another pass already accepted - that is godmode-second-look.

Deterministic Execution Flow

  1. Licence first. godmode license check --operation "<the survey, naming the source>" - whether an operation naming that source may proceed at all. Then read the licence file with a receipt: godmode read --source <name> --path LICENSE --root <local checkout of the source>, and classify it: godmode license attest --repo <name> --classification <permissive|proprietary-no-redistribution|unlicensed|copyleft-incompatible> --clean-room-note "<what was read versus written>" (the note is required for anything but permissive).
    • Fallback: a refusal from license check, or a classification other than permissive, ends the survey at import_verdict: skip - record that and stop.
  2. Tree, then the implementing files. List the source's tree and name the two or three files that implement the claimed mechanism. godmode upstream --path <local checkout> --skills <keyword> lists the skill and doc files that mention the mechanism, with line numbers, and records nothing - a pointer to where the code lives, never a substitute for reading it.
  3. Receipt every implementing file. godmode read --source <name> --path <implementing file> --root <local checkout> --lines <a-b> - one receipt per file opened: path, line range, and a digest of the slice.
  4. Measure the reading depth. godmode parity --sources - per source, files_opened and surface_only. A source still surface_only: true has not been read; go back to step 3.
  5. Record both verdicts. godmode remember --kind decision --subject "absorb:<name> <date>" --value "<finding> import_verdict: <adopt|extend|diverge|skip|exists|unread|n-a> behaviour_verdict: <confirmed-have|confirmed-dont|unverified>" --evidence receipt:<name>:<implementing file> - refused surface-only when adopt or extend cites only README, docs or release-note receipts, and refused naming either missing verdict.
  6. Dispose each symbol with no counterpart when comparing a copied tree. godmode upstream --path <local checkout> --dispose <SYMBOL>=<adopt|extend|diverge-deliberately|n-slash-a-different-surface>:<confirmed-we-have-it|confirmed-we-dont|unverified> --evidence receipt:<name>:<file>.

Read PURPOSE.md for the archive records this skill exists to close.

Must Not

  • Never record adopt or extend from a README, doc or release-note reading; the verdict for a surface read is unread, skip or diverge.
  • Never study a source's code before its licence is classified in step 1; instead classify the licence first and stop if it forbids the use.
  • Never name the studied source in shipped text (code, docs, skills, changelog); instead describe the mechanism in Godmode's own words and keep the name in the private record.
  • Never copy source text into this repository; a mechanism is carried over only by godmode-replicate, rewritten under Godmode names.
  • Never skip the receipt for a file that the verdict relies on; an unreceipted read is invisible to parity --sources.

Acceptance

  • godmode parity --sources reports surface_only: false for every source whose verdict is adopt or extend.
  • Every absorb: decision carries both verdicts and at least one receipt naming a source file.

If an assertion cannot be proved, report the unmet assertion and the next safe action rather than the outcome it was meant to prove.

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.