agentleFS
Sign inStart free
tonmoy007tonmoy007/forge-plugins/skills/forge-watch/SKILL.md

watch

Skill2 starsChanged 5 months agoMITView on GitHub

Start the Forge Observer — a background daemon (Stage 9) that periodically

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use decision-map, map 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.
  • Mathews-TomSkill

    decision-map

    Use when mapping unresolved architecture, policy, or scope decisions before planning, or working one decision ticket, including a prototype ticket whose throwaway evidence the prototype package builds. Also applies to "map the decisions", "decision map", and "wayfinder". Not for implementation slices of a known feature, milestone plans, general UI generation, standalone prototypes outside a decision map (use prototype), or adopting experimental code into production.

    Also in 3 projects that use this

  • AWSSkill

    map

    Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.

    Also in 3 projects that use this

  • dubwoahSkill

    ask

    Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.

    Also in 3 projects that use this

  • javatarzSkill

    wiki

    Access and manage the local GitHub Wiki clone. Use this skill when you need to read wiki content (architecture, design docs, guides), update wiki documentation, check wiki status, or push wiki changes. The wiki contains high-level system design and architectural documentation.

    Also in 3 projects that use this

  • renatorozasSkill

    grill

    Adversarial code review. Don't let me ship until the changes pass your scrutiny.

    Also in 3 projects that use this

  • VercelSkill

    setup

    Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".

    Also in 7 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a long build session, to start accumulating Observer findings for next time.

    line 23
  2. Distinctive:

    Start (or confirm) the Observer:

    line 34

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

Forge Watch — start the Observer

Starts the Observer daemon (REQ-F-008..014). Idempotent: starting an already-running Observer warns instead of spawning a second session. The Observer reuses a single claude -p session (resumed each poll) pinned to a cheap model, and writes only to .forge/ — it never touches pipeline artifacts.

When to Use

  • User types /forge:watch or asks to monitor/watch the project in the background.
  • After a long build session, to start accumulating Observer findings for next time.

When NOT to Use

  • The user wants a one-off review of changes now → that's /forge:review, not the background watcher.
  • Background agents are unavailable — the command is safe (clean no-op) but pointless; /forge:status will show "Observer: not running".

Steps

  1. Start (or confirm) the Observer:
    python3 ${CLAUDE_PLUGIN_ROOT}/scripts/observer.py --start --cwd "$(pwd)"
  2. Present the one-line result verbatim. Possible outcomes:
    • started — "Observer watching (session …); N finding(s) on first poll".
    • already_running — it was already watching; do not start a second one.
    • unavailable — background agents are off; tell the user it's a no-op and that findings won't accrue until a background-capable claude is present.
  3. Mention that findings surface automatically at the next session start and in /forge:status, and that /forge:watch-stop stops it.

Verification

  • python3 ${CLAUDE_PLUGIN_ROOT}/scripts/observer.py --status --cwd "$(pwd)" shows "Observer: running …" after a successful start.
  • Re-running /forge:watch reports already_running (no duplicate session).

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