ワンクリックでManusで任意のスキルを実行

janitor-issues-watch-off

スター1

フォーク1

更新日2026年7月11日 11:46

Turn OFF GitHub issue monitoring for THIS project - the heartbeat stops notifying you about new issues and new comments on the tracker. Use when the user says "stop watching the issues", "disable issue notifications", "turn off the issue tracker monitoring", "too many github issue notifications".

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Emasoft

Emasoft/ai-maestro-janitor

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Janitor issues-watch OFF

Overview

Turns OFF the github-issues-watch detector (TRDD-2KQQAEPP) for THIS project by removing its opt-in sentinel. The detector then costs one stat per fire and prints nothing.

Instructions

Remove the opt-in sentinel:
```
STATE_DIR="${CLAUDE_PROJECT_DIR:-$(pwd)}/.janitor/state"
rm -f "$STATE_DIR/issues-watch.flag"
```
The seen-map (issues-watch-seen.json) is deliberately LEFT in place. It is a tiny cache, not user work, and keeping it means re-enabling later resumes from where you left off instead of re-baselining. /janitor-issues-watch-on overwrites it anyway.
Report one line: issue notifications are off for this project.

Output

One line to the user. Removes .janitor/state/issues-watch.flag.

Scope

ONLY this project. Does NOT disarm the heartbeat, stop the daemon, touch other projects, or change anything on GitHub. Re-enable with /janitor-issues-watch-on.

Resources

${CLAUDE_PLUGIN_ROOT}/scripts/detectors/github-issues-watch.py — the detector this sentinel gates.

このリポジトリの他の Skills

同じリポジトリ

janitor-memory-consolidate

Emasoft/ai-maestro-janitor

CONSOLIDATE (MERGE) executor — fuses two duplicate memory notes about the SAME subject + same type into one page (dedup lessons, redirect backlinks, keep the oldest origin date), through the crash-safe transaction core, never editing a live page. ABSTAINS on uncertainty, cross-type/cross-scope/two-hub, or a third page sharing the subject. Use on a [janitor-memory-consolidate] marker, or "consolidate / merge / deduplicate the memory", "two notes cover the same thing", "fold these memory pages together".

2026-07-261

janitor-memory-recall

Emasoft/ai-maestro-janitor

RECALL — before working on a file or debugging/deciding, surface the right memory WIKI page and navigate it. Two entry points - FILE-anchored (about to edit a file → surface that functionality's HUB page and descend its links to the detail needed) and SYMPTOM ("have we hit this before?" → rank pages by how the symptom hits their description/title/tags). Use before re-deriving architecture/gotchas, or when the user says "recall memories about X" or "did we already solve this". Reads only the pages the task needs, degrading to grep when memgrep is absent. The RECALL leg of the wiki-memory protocol.

2026-07-261

janitor-memory-write

Emasoft/ai-maestro-janitor

MEMORIZE — capture a durable decision/fact into the project's memory WIKI as a navigable page, not a loose note. Use after a bug-autopsy gotcha, a design/architecture decision, a project constraint not derivable from code, a confirmed user preference, or when the user says "remember this", "memorize this", "save a memory". Finds the right existing wikimem page first so it never duplicates; only when none fits, creates a HUB / ASPECT / COMPONENT page via the expand/reduce decision, wires it into the See-also web, and indexes it by symptom. The MEMORIZE leg of the wiki-memory protocol.

2026-07-261

janitor-memory-update

Emasoft/ai-maestro-janitor

UPDATE — modify an existing memory WIKI page when something changes — ADD a decision to the page that owns the subject, CORRECT a memory a new discovery contradicts (the 2-step non-destructive protocol), or RESHAPE a page that outgrew its tier (expand a shared rule into an aspect, reduce element-specific detail into its component page). Use when a decision changes, a memory turns out wrong, a page mixes too many subjects, or the user says "update the memory", "that's no longer true", "fix the note about Y", "this memory is outdated". Keeps the See-also web, the hub map, and the lessons trail consistent. The UPDATE leg of the wiki-memory protocol.

2026-07-261

janitor-auto-manage-oauth-on

Emasoft/ai-maestro-janitor

Opts THIS machine into the janitor's unattended multi-account OAuth rotator. Sets an opt-in flag the always-on janitor daemon's 60s oauth-rotator-tick Task reads to rotate the live Claude Code credential to an alternate paid account before a rate-limit 429 stalls an overnight session. Default OFF, macOS only, idempotent; refuses if a pinning env var would defeat rotation. Trigger with /janitor-auto-manage-oauth-on, "turn on oauth rotation", or "enable account rotator".

2026-07-261

janitor-token-attribution

Emasoft/ai-maestro-janitor

Rank every project on this machine by how many tokens it is burning right now and name the one to throttle — the fleet token-attribution dashboard. The account 5h/7d utilization% is aggregate across all your parallel projects; this scans each project's transcripts to say WHICH one is over-consuming (large 5h share AND above its own baseline) and where its spike came from. Read-only. Use when the user asks which project is eating the token budget / which session to throttle / who is burning the rate-limit window.

2026-07-261

name	janitor-issues-watch-off
description	Turn OFF GitHub issue monitoring for THIS project - the heartbeat stops notifying you about new issues and new comments on the tracker. Use when the user says "stop watching the issues", "disable issue notifications", "turn off the issue tracker monitoring", "too many github issue notifications".

Janitor issues-watch OFF

Overview

Turns OFF the github-issues-watch detector (TRDD-2KQQAEPP) for THIS project by removing its opt-in sentinel. The detector then costs one stat per fire and prints nothing.

Instructions

Remove the opt-in sentinel:
```
STATE_DIR="${CLAUDE_PROJECT_DIR:-$(pwd)}/.janitor/state"
rm -f "$STATE_DIR/issues-watch.flag"
```
The seen-map (issues-watch-seen.json) is deliberately LEFT in place. It is a tiny cache, not user work, and keeping it means re-enabling later resumes from where you left off instead of re-baselining. /janitor-issues-watch-on overwrites it anyway.
Report one line: issue notifications are off for this project.

Output

One line to the user. Removes .janitor/state/issues-watch.flag.

Scope

ONLY this project. Does NOT disarm the heartbeat, stop the daemon, touch other projects, or change anything on GitHub. Re-enable with /janitor-issues-watch-on.

Resources

${CLAUDE_PLUGIN_ROOT}/scripts/detectors/github-issues-watch.py — the detector this sentinel gates.