agentleFS
Sign inStart free
sandraschisandraschi/handbrakemcp/.github/copilot-instructions.md

handbrakemcp

Copilot instructions2 starsChanged 10 days agoMITView on GitHub

You have video transcoding tools via HandBrakeCLI: transcodevideo, batchtranscode, job monitoring. Before starting work: 1. Check provider health: getproviderstatus() 2. List presets for the task: get_presets() At end of work: - Report job IDs and final getjobstatus() for any transcodes started - Note failed jobs with their error strings - Canonical live server: src/handbrakemcp/server.py (handbrakemcp.server:app). src/handbrake_mcp/main.py is the legacy/Docker entry — prefer server.py. - Responses are dialogic dicts with success/message; shared errors go through errorresponse() in tools/utilitytools.py (logs via logger.exception).…

We split this copilot-instructions.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check provider health: get_provider_status()

    line 8
  2. Very specific:

    Never use bare except: pass (ruff S110/S112 are enforced, not ignored).

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 3,669 Copilot instructions 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
copilot-instructions.md

Copilot instructions — handbrake-mcp

Session Context (HandBrake MCP)

You have video transcoding tools via HandBrakeCLI: transcode_video, batch_transcode, job monitoring.

Before starting work:

  1. Check provider health: get_provider_status()
  2. List presets for the task: get_presets()

At end of work:

  • Report job IDs and final get_job_status() for any transcodes started
  • Note failed jobs with their error strings

Repo notes

  • Canonical live server: src/handbrake_mcp/server.py (handbrake_mcp.server:app). src/handbrake_mcp/main.py is the legacy/Docker entry — prefer server.py.
  • Responses are dialogic dicts with success/message; shared errors go through _error_response() in tools/utility_tools.py (logs via logger.exception).
  • Never use bare except: pass (ruff S110/S112 are enforced, not ignored).
  • Ports: backend 10875, frontend (web_sota/) 10874 — never hardcode others.

Download now (ZIP)

  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,297 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository9 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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