agentleFS
Sign inStart free
boston-harness-groupboston-harness-group/remote-factory/skills/study/SKILL.md

study

Skill74 starsChanged 38 days agoMITView on GitHub

Analyze the current codebase using Factory's observation engine and code graph. Generates a report covering code quality, eval scores, structural analysis, open issues, backlog items, observability coverage, and improvement opportunities. Use when the user wants to understand the state of their project before making changes.

20 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Check whether a code knowledge graph is available by running factory graph status "$(pwd)".

    line 24
  2. Distinctive:

    If the graph is available (status shows node/edge counts), explore the code graph:

    line 26
  3. Very specific:

    Write graph findings to .factory/strategy/graph-context.md, then combine:

    line 34
  4. Very specific:

    After studying, use /factory:implement to act on the findings.

    line 57

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

/factory:study

Analyze the current codebase and generate an observation report with structural graph analysis.

Prerequisites

command -v factory >/dev/null 2>&1 || uv tool install "${CLAUDE_PLUGIN_ROOT}"

Execution

factory graph update "$(pwd)"
factory study "$(pwd)"

Check whether a code knowledge graph is available by running factory graph status "$(pwd)".

If the graph is available (status shows node/edge counts), explore the code graph:

factory graph query "$(pwd)" "<focus from observations>" --depth 2
factory graph explain "$(pwd)" "<key node>"
factory graph path "$(pwd)" "<A>" "<B>"

Write graph findings to .factory/strategy/graph-context.md, then combine:

cat .factory/strategy/observations.md .factory/strategy/graph-context.md \
  > .factory/strategy/study-combined.md

The combined report at .factory/strategy/study-combined.md covers:

  • Eval scores — current composite and per-dimension breakdown
  • Open issues — from GitHub, if available
  • Backlog items — pending work from .factory/strategy/backlog.md
  • Observability coverage — logging density and uninstrumented files
  • Hypothesis budget — how many improvements to target this cycle
  • Cross-project insights — patterns from sibling projects (if any)
  • Structural analysis — key modules, dependency paths, architectural layers, entry points

For cross-project insights, pass --projects-dir:

factory study "$(pwd)" --projects-dir ~/factory-projects

After studying, use /factory:implement to act on the findings.

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