Remove project-specific src/cleveragents/ path (now src/<package>/ with
examples). Replace all bare nox/Pyright/ruff/Behave references with the
language-agnostic 'task runner / type checker / linter / BDD framework'
abstractions, keeping the project-specific tool as a parenthetical example.
Add ecosystem-equivalents reference table (Python, JS/TS, Java/Kotlin, Go)
in the Quick Command Reference. Generalise type-suppression rules across
languages (# type: ignore, @ts-ignore, @SuppressWarnings). Generalise
TDD assertion failure type requirement with Python, Java, and JS examples.
Generalise import rules, project manifest references, and directory layout
descriptions. Remove Python-only step-file naming; add multi-language
examples throughout.
LangChain/LangGraph and v3/legacy plan workflow sections are left as-is
and clearly labelled as project-specific.
ISSUES CLOSED: #0
Added 11 new decision trees (branch naming, documentation traceability,
nox session guide, CI failure diagnosis, file organization, dev setup,
Issue/Epic/Legendary hierarchy, ticket well-scoped checklist, v3 vs
legacy plan workflow, release process, TDD issue-capture test detail).
Expanded existing trees with previously missing rules: specification-
first development mandate, file organization per directory, backwards
compatibility policy (none pre-v3.0.0), AssertionError-only rule for
TDD expected-fail steps, tdd/mN- and bugfix/mN- branch naming with
shared suffix requirement, different-assignees preference for TDD vs
fix, full CI job list with required-for-merge gates, all nox sessions
(e2e_tests, benchmark, benchmark_regression, complexity, docs, build).
Fixed PR approval count from 2 to 1 (project-specific override; self-
approval permitted per CONTRIBUTING.md). Updated Key Numbers table with
12 new rows covering CI triggers, release trigger, ULID format, required
CI jobs, backwards compat start, dependency direction, and more.
ISSUES CLOSED: #0
forgejo-label-manager.md:
- Refactored curl permission rules to use explicit allow/deny ordering with
clear comments explaining each rule; consolidated overlapping deny patterns
- Switched to curl-only approach via forgejo-api skill (deny all Forgejo MCP tools)
- Added read: deny and skill forgejo-api: allow to enforce the curl-only model
- Clarified permission block structure: deny by default, specific allows per endpoint
pr-merge-pool-supervisor.md:
- Expanded 'What You Receive' section to list each field individually with bold
labels for clarity (owner, repo, PAT, git email/name, briefing)
product-builder.md:
- Added 'Local Variable' column to the Required Information table so agents know
the canonical variable names to reuse throughout prompts
- Added forgejo_url, forgejo_owner, and forgejo_repo as explicit gather targets
with env var fallbacks and remote-detection instructions
- Added concrete remote URL parsing example showing how to extract host/owner/repo
Fixes and improvements from exhaustive audit:
Consistency fixes in SKILL.md:
- 'Pipe & Filter' → 'Pipe and Filter' (one stray '&' found and corrected)
- 'Singleton for factory instance' → clarified to 'register factory as
singleton-scoped via DI container' (less misleading wording)
- Documentation Format section updated with note that SKILL.md itself is the
authoritative source for related-pattern combinations
Coverage fix — Related Patterns sections:
- Added '## Related Patterns' to ALL 94 pattern files (was 0/94)
- Each section lists 3–6 related patterns with relationship descriptions
- Covers: why they're related, when to prefer one vs the other,
and which are often confused
SOLID principles → Creational → Structural → Behavioral → Architectural →
Concurrency → Functional → Resilience → Data Access → Messaging →
Testing → Error Handling → Microservice — all 13 categories covered
Code verification:
- Python: 0 failures (all 85 testable blocks pass)
- Go: 0 failures (all 76 testable blocks pass)
- JavaScript: 0 failures (all 78 testable blocks pass)
- All 239 code blocks verified correct after edits
Final skill state:
- 108 files, 36,524 lines across 13 reference categories
- 94/94 pattern files have Related Patterns sections
- 2,815-line SKILL.md with 67 decision trees, 23 scenarios,
0 broken references, 0 naming inconsistencies
- 476 → 1,569 → 2,244 lines total growth
- Decision trees: 6 → 34 → 51 situation-specific trees
- Compound scenarios: 12 → 18 full architecture maps
- New trees added in this pass:
search/discovery, game/simulation, feature flags, subscriptions/billing,
soft delete/archiving, i18n/localization, database optimization,
AI agents/LLM systems, file upload/media, CMS, OAuth2/SSO,
graph traversal, audit/compliance, real-time collaboration,
API versioning, bulk/batch processing, pagination/filtering,
webhook delivery (17 new trees)
- New scenarios added:
user registration with email verification, faceted search,
feature flag system, shopping cart with session, rate limiting
infrastructure, AI agent with tool use (6 new scenarios)
- New sections:
'Pattern Progression' (5-stage evolution for a data service and flag)
'Minimum Pattern Set per Component Type' (table of 15 component types)
'When to Skip Patterns — Never' table expanded to 25 rationalizations
- All file references validated (0 broken)
Approved proposal: #7602
Pattern: workflow_fix
Evidence: Watchdog (Cycle 15, #7587) reports HIGH severity systemic issue —
AUTO-REV-SUP creating 10+ duplicate tracking issues per cycle. Root cause:
agent definition uses AUTO-REV-POOL prefix in ATM calls but actual issues
use AUTO-REV-SUP prefix. ATM cannot find/close old issues → duplicates.
Fix: Updated all tracking prefix references from AUTO-REV-POOL to AUTO-REV-SUP
and tracking type from 'Review Pool Status' to 'PR Review Pool Status'.
ISSUES CLOSED: #7602
# Conflicts:
# .opencode/agents/pr-review-pool-supervisor.md
- Fix grooming-worker Forgejo permissions (deny → allow) to unblock direct API calls
- Route PR label fetching through forgejo-label-manager subagent
- Replace priority-alignment check with milestone enforcement (every issue must have a milestone)
- Add step 11: address non-code review remarks (labels, description, milestone) during grooming
- Clarify grooming-pool-supervisor stale threshold to explicit 24-hour window
- Refactor pr-merge-pool-supervisor main loop into explicit numbered steps
- Add triage strategy section emphasising parallel review checks and immediate worker dispatch
- Tighten merge criteria: explicit APPROVED state, no unresolved REQUEST_CHANGES on current head
- Dispatch workers for all PR processing, not only rebase operations
- Add rule to batch forgejo_list_pull_reviews calls instead of checking serially
Renamed backlog-grooming-pool-supervisor to grooming-pool-supervisor and
backlog-grooming-worker to grooming-worker. The grooming agents now analyze
all open issues AND pull requests (not just the backlog). Workers perform a
full 10-point quality analysis on a single item instead of processing
batches. PRs with unaddressed reviews are prioritized. PR labels are synced
from linked issues. Workers post [GROOMED] markers for tracking.
Fixed critical issue: implementation-pool-supervisor now correctly dispatches
workers through tier selectors (tier-haiku/codex/sonnet/opus) instead of
launching implementation-worker directly, ensuring the escalation model
actually sets the correct model tier. Added implementation-worker to all
four tier selector task permissions.
Updated session tags from AUTO-BLOG to AUTO-GROOM. Updated specification
sections 4.2.1, 5.5, 5.5.1, 9.7, and architecture diagram.
ISSUES CLOSED: n/a
Complete the tracking prefix fix by updating all remaining references:
- Embedded CREATE_TRACKING_ISSUE call (lines 195-196)
- REVIEW_OWN_ANNOUNCEMENTS call (line 219)
- CLOSE_ANNOUNCEMENT_ISSUE call (line 225)
All 8 instances of AUTO-BUG-SUP are now consistent throughout the file.
Previously the product-builder would adopt existing supervisor sessions
from prior runs and skip launching those already running. This caused
stale sessions to persist with outdated configuration and context.
Now Phase C.0 discovers and gracefully stops all existing supervisor
sessions before Phase C.2 unconditionally launches all 18 fresh.
The pr-reviewer agent was falling back to Forgejo MCP tools for reads
instead of using curl, causing actions to be attributed to the wrong
user account. This change:
- Blocks ALL Forgejo MCP tools (forgejo: '*': deny) instead of only
specific write tools
- Adds explicit curl-only mandate section with clear explanation
- Adds tested curl command reference covering every API operation
the reviewer needs (PR details, diffs, issues, CI status, reviews,
file contents, posting reviews, posting comments, dismissals)
- Adds robots.txt override instruction for our self-hosted instance
- Updates all review process steps to reference curl instead of MCP
The product-builder now reads FORGEJO_REVIEWER_* env vars and passes them
as the sole credentials to pr-review-pool-supervisor, which passes them
through to pr-reviewer workers. No agent in the review chain receives the
primary bot credentials, preventing accidental self-approvals. Simplifies
the reviewer instructions to require formal PR reviews (not just comments)
and removes contradictory references to denied MCP write tools.
Approved proposal: #7523
Pattern: prompt_improvement
Evidence: Agent definition specified [AUTO-BUG-POOL] prefix and 'Bug Detection
Report' tracking type, but actual tracking issues use [AUTO-BUG-SUP] prefix
and 'Bug Hunt Status' type (e.g., issue #7470). Watchdog health audit also
references AUTO-BUG-SUP. Definition was out of sync with actual behavior.
Fix: Updated all tracking prefix references from AUTO-BUG-POOL to AUTO-BUG-SUP
and tracking type from 'Bug Detection Report' to 'Bug Hunt Status'.
ISSUES CLOSED: #7523
- pr-reviewer.md: renamed "PR Self-Reviewer" to "PR Reviewer", rewrote
APPROVE and REQUEST_CHANGES templates to use curl with FORGEJO_REVIEWER_PAT
instead of denied MCP tools, corrected step ordering (formal review first,
backup comment second)
- pr-review-pool-supervisor.md: added all 3 reviewer credentials to stuck-PR
prompt which was missing them entirely
The Forgejo MCP tools authenticate with a single server-level token that
cannot be overridden per-call. The PR Reviewer must use curl with
FORGEJO_REVIEWER_PAT for write operations (reviews, comments) to
authenticate as the reviewer account.
- pr-reviewer.md: added curl allow, denied MCP write tools, added
curl-based review/comment API patterns with FORGEJO_REVIEWER_PAT
- pr-review-pool-supervisor.md: passes all 3 reviewer creds, documents
READ-via-MCP/WRITE-via-curl split
- product-builder.md: passes FORGEJO_REVIEWER_PASSWORD to review pool
Solves the "shared bot account problem" by introducing a separate Forgejo
reviewer account (FORGEJO_REVIEWER_PAT / FORGEJO_REVIEWER_USERNAME).
- pr-reviewer.md: rewrote review protocol to use reviewer credentials,
formal APPROVED reviews are now the primary path (not a workaround)
- pr-review-pool-supervisor.md: passes reviewer credentials to dispatched reviewers
- pr-merge-pool-supervisor.md: updated approval detection to recognize
reviewer account as primary approver
- product-builder.md: passes reviewer creds when launching review pool
- shared/credential_security.md: added FORGEJO_REVIEWER_PAT and
FORGEJO_REVIEWER_USERNAME to required credentials
Per Subagent Specialization Principle: removed 17 duplicated rolling
average calculation blocks from all supervisors. The ATM now handles
interval calculation internally via --sleep-interval-default parameter.
- automation-tracking-manager.md: added sleep_interval_default to CREATE_TRACKING_ISSUE,
added CYCLE_ANNOUNCEMENT_REVIEW operation (#11)
- All 17 supervisor agents: replaced 7-line interval calc with --sleep-interval-default param
- shared/tracking_discovery_guide.md: updated to reference ATM-handled interval
Added the **Estimated Cycle Interval** field to the actual tracking body
template strings in all 14 agents that had inline body strings without it.
Fixed 2 non-standard body formats (project-owner had [HEALTH] header,
bug-hunt had no header). All 18 status-creating agents now produce tracking
issues with the standardized header including the interval field.
All 17 supervisor/orchestrator agents had CREATE_TRACKING_ISSUE before
READ_TRACKING_STATE in their tracking operations reference. This wrong
ordering causes agents to destroy state before recovering it. Fixed all
to: READ (recover state) -> calculate rolling interval -> CREATE (new issue).
Each agent now includes:
- Startup recovery with READ_TRACKING_STATE as step 1
- Rolling average interval calculation with agent-specific defaults
- Note that tracking body MUST include Estimated Cycle Interval field
- automation-tracking-manager.md: added estimated_cycle_interval to READ_TRACKING_STATE return
- system-watchdog-pool-supervisor.md: replaced hardcoded interval lookup with parsing from
status issue body, changed staleness threshold from 1.2x to 2x
- backlog-grooming-pool-supervisor.md: added Pass 20 for duplicate status issue deduplication
- shared/tracking_discovery_guide.md: added rolling average calculation pattern
- automation-tracking-manager.md: enhanced READ_TRACKING_STATE to return full
comments, creation timestamp, and offline duration for crash recovery
- implementation-pool-supervisor.md: added state recovery as mandatory first
action (before PR analysis), with branch/PR target extraction and resume logic
- product-builder.md: replaced manual curl state detection with ATM
READ_TRACKING_STATE for consistent crash recovery
- shared/tracking_discovery_guide.md: added mandatory startup recovery protocol
documenting the correct read-then-delete-then-create sequence
freemo
HAL9000
CleverAgents Build Agent
clever-agent