32 Commits

Author	SHA1	Message	Date
freemo	1885990081	build: auto opencode agents rewritten	2026-04-27 12:49:08 -04:00
freemo	59a2a83328	build: fixed pr-merge filtering to avoid non-mergable PRs	2026-04-18 01:41:40 -04:00
freemo	e8f06fa433	build: made invocation of scripts more explicit	2026-04-17 16:32:37 -04:00
freemo	d6fca18c01	build: broke the 4 stage pr merge cycle into a 6 stage cycle and eliminating PRs that arent stale and need review	2026-04-17 14:20:40 -04:00
freemo	afa4ebd19b	build: fixed up the systems skill so it now provides better access to information about scripts to ensure more consistent usage	2026-04-17 12:50:46 -04:00
freemo	6dad967130	Build: fixed systems skill to link to the scripts from the main skill page	2026-04-16 22:41:42 -04:00
freemo	588199886e	build: wrong name for auto-agents system skill	2026-04-16 19:53:09 -04:00
freemo	438df82caa	build: changed pr-merge process (including supervisor) to use new skills and scripts	2026-04-16 19:10:04 -04:00
freemo	ac702cc375	build: Added script to initiate the merge	2026-04-16 18:50:59 -04:00
freemo	d3e0911f86	build: added script for rebasing on server to system skill	2026-04-16 18:17:15 -04:00
freemo	703cf13c01	build: removed rules skills, its in the system skill	2026-04-16 18:01:14 -04:00
freemo	a58d17416c	build: added scripts into auto-agents-system skill for getting the PR categories for merging.	2026-04-16 17:59:56 -04:00
freemo	dceb0e91d3	docs(skill): add cleveragents-agent-rules universal agent rules skill ... Introduces a new skill containing the complete specification for the five universal operational rules every agent must follow: exhaustive pagination protocol, label management via forgejo-label-manager, bot signature format, credential flow hierarchy, and localhost:4096 restriction.	2026-04-16 01:00:48 -04:00
freemo	c9dc70004c	docs(skill): add full redundancy and self-healing documentation to cleveragents-system skill ... Add new references/redundancy/README.md (280 lines) covering: - Three-layer redundancy architecture overview (product-builder / watchdog / supervisors) with the key insight that each layer uses a different observation mechanism to prevent blind spots between layers - Layer 1 (product-builder): fast cycle (60s liveness), deep inspection (5-min message reading with anti-pattern catalogue: error loops, circular patterns, policy violations, context exhaustion), worker health check (pool count vs expected), hourly verification - Layer 2 (system-watchdog): independent 5-min audit using Forgejo tracking issue STALENESS rather than OpenCode session status — catches frozen-but-alive sessions that appear healthy to product-builder; session introspection for anti-pattern detection; clear role separation (watchdog detects, product-builder restarts) - Layer 3 (supervisor self-monitoring): per-cycle worker health checks, stuck detection (15-min threshold), completed vs crashed distinction, pool filling - State persistence as the foundation of self-healing: everything externalized to Forgejo (tracking issues, attempt comments, claim protocol, announcements) - Supervisor crash-recovery pattern: session crash → product-builder detects ≤60s → relaunch → READ_TRACKING_STATE first → light/moderate/full recovery based on offline duration → resume from recovered state - Worker crash-recovery pattern: crash → supervisor detects in next cycle → Forgejo evidence check → re-dispatch at same or escalated tier - Two independent health signals table: OpenCode (session presence/status, latency 60s) vs Forgejo (tracking staleness, latency 2×interval) — what each catches - Complete failure mode catalogue (13 failure types with: who detects it, how, recovery action, and whether recovery is automatic or requires human) - async-agent-monitor health classifications: healthy/stuck/idle/finished/errored with threshold and configurable idle_threshold_minutes parameter - Redundancy gaps and limitations: product-builder has no watcher; watchdog detects but cannot restart; worker downtime latency varies by supervisor sleep Expand SKILL.md (539 → 775 lines, 10 → 13 decision trees): - Significantly expand 'Is something wrong?' tree: now lists every failure type with which layer detects it, how detection works, and recovery action (supervisor missing, frozen, error loop, waiting for input, worker crashed, worker frozen, supervisor stopped dispatching, orphaned claim, CI violations, multiple supervisors down, product-builder crash) - Add new 'How does the system self-heal?' tree: full three-layer redundancy decision tree with per-layer mechanics (fast/deep/hourly cadences), the Forgejo persistence foundation, complete supervisor crash-recovery pattern, complete worker crash-recovery pattern, and the single-point-of-failure note - Update Key Numbers table: add worker health check and hourly cycle entries; clarify session health threshold is configurable; add watchdog staleness threshold (2×interval); add supervisor max downtime (≤60s); add worker re-dispatch latency (varies by sleep interval) - Update frontmatter description to cover self-healing and redundancy - Update reference index to describe the new redundancy reference file ISSUES CLOSED: #0	2026-04-15 20:18:54 +00:00
freemo	e1e65c85ae	docs(skill): final cleanup pass — remove remaining duplicated project knowledge, cross-reference other skills ... agent-registry/README.md: - Remove typecheck-fixer 'Never uses type: ignore' rule (contributing rule, lives in cleveragents-contributing not the system registry) - Remove coverage-improver '>=97%' threshold (project-specific threshold, lives in cleveragents-contributing) - Change new-issue-creator description from 'following CONTRIBUTING.md format' to 'following the project issue format' with cross-reference pointer - Remove subtask-loop trivial description; expand to show the full implement → test → quality gates → review loop it manages - Remove duplicate forgejo-label-manager entry ('See above.') — was listed twice in the utility subagents table - Add cross-reference note at top of Utility Subagents section: descriptions focus on system role; project-specific rules (testing philosophy, quality gates, commit standards, issue format) are in cleveragents-contributing - AUTO-IMP-SUP dispatch ordering: add inline cross-reference note pointing to cleveragents-contributing and cleverthis-guidelines for label definitions - AUTO-OWNR description: replace specific label names ('MoSCoW labels', 'Wont Do') with generic role description + cross-reference note SKILL.md: - Reference Index: fix tracking-system entry description — remove 'label rules' (those were removed from tracking-system last pass); replace with accurate description of what the file now covers (Automation Tracking and needs feedback labels as system-specific labels) No system-specific content was removed: all agent prefixes, the full announcement relevancy matrix, worker tag patterns, sleep intervals, worker count formulas, tier system mechanics, tracking system operations, credential propagation hierarchy, and claim/heartbeat/release protocol are fully preserved. ISSUES CLOSED: #0	2026-04-15 20:13:47 +00:00
freemo	e816e1af9e	docs(skill): final pass — expand relevancy matrix, remove duplicated knowledge, cross-reference other skills ... SKILL.md: - Expand 'Which announcements should I consume?' from a partial example (only showed IMP-SUP and said 'use agent-prefix-info for the rest') to the FULL canonical cross-agent attention table: all 17 supervisors plus product-builder, every source prefix with its minimum priority threshold and rationale, universal baseline rule, and rule-of-thumb note - 'How do I apply a label?' tree: replace detailed label scope breakdown (State/, Priority/, MoSCoW/, Type/) and detailed forgejo-label-manager internals with cross-references to cleveragents-contributing and cleverthis-guidelines; keep only system-critical labels (Automation Tracking, needs feedback, Blocked) and the forbidden operations list (which is an agent permission concern unique to this system) - 'How does a supervisor launch a worker?' Step 5: replace 'CONTRIBUTING.md rules (commit standards, testing, PR requirements)' with reference to the cleveragents-contributing skill, noting that product-builder pre-loads these via ref-reader and passes them in briefings - Quick Reference: add explicit pointers to cleveragents-contributing and forgejo-api skills for the label-related lines - Frontmatter description: rewrite Covers section to remove duplicated label scope and forgejo-api curl content; add explicit note that label rules and scopes live in cleveragents-contributing and cleverthis-guidelines, and that curl patterns are in the forgejo-api skill tracking-system/README.md: - Remove entire 'Label Rules (CRITICAL)' section (Never Create Labels, Only Org-Level Labels, Always Use forgejo-label-manager, scope conflict rules) — this is fully covered in cleveragents-contributing - Remove entire 'The forgejo-api Skill and Label Operations' section (paginated org label fetch loop, PUT replace-all curl, DELETE single label curl) — this belongs in the forgejo-api skill which forgejo-label-manager loads automatically - Replace both removed sections with a focused 'System-Specific Labels' section covering only what is unique to the system: Automation Tracking as the universal discovery mechanism and needs feedback as the human escalation signal that stops worker dispatch - Priority labels table: change from defining what each priority level IS (duplicates cleverthis-guidelines) to showing when to use each for autonomous system announcements specifically; add cross-reference note coordination/README.md: - Remove duplicated 'Announcement Relevancy Matrix Quick Reference' table (9 rows covering only some supervisors) — the full authoritative table is now in SKILL.md; replace with a two-sentence pointer to SKILL.md and agent-prefix-info for programmatic lookup ISSUES CLOSED: #0	2026-04-15 20:08:35 +00:00
freemo	2dbcdc80ae	docs(skill): add cleveragents-system self-reflection skill ... New skill covering the complete operational architecture of the CleverAgents autonomous development system — how it runs, not what it builds. SKILL.md (539 lines) with 9 decision trees: - 'What does this agent do?' — prefix-to-agent mapping for all 17+1 supervisors - 'Which supervisor owns this worker?' — reverse lookup from worker tags - 'How many workers can this supervisor run?' — N_FULL/N_HALF/N_QUARTER formula with concrete examples at N=4, N=8, N=16 - 'How does a supervisor launch a worker?' — full dispatch flow including tier selector indirection, model inheritance, and credential inclusion - 'Do I need to launch something asynchronously?' — when/why to use prompt_async vs synchronous calls; why only async-agent-manager calls localhost:4096 - 'How do I apply a label to an issue or PR?' — forbidden operations list; forgejo-label-manager delegation; org-level vs repo-level; never create - 'How do I create a tracking issue or announcement?' — CREATE_TRACKING_ISSUE invariants; READ-then-CREATE startup order; announcement lifecycle - 'Which announcements should I consume?' — full relevancy matrix per agent type - 'How does state recovery work on startup?' — mandatory READ-then-CREATE protocol with urgency tiers based on offline duration - 'Which model tier should I use?' — escalation decision logic with comment parsing - 'How do credentials get to workers?' — env var hierarchy; why workers never read env vars; two bot accounts (primary + reviewer) - 'Is something wrong with the system?' — diagnostic patterns Complete supervisor registry table (17 supervisors + product-builder) with prefixes, agent definitions, worker counts, sleep intervals, and tracking prefixes. Key Numbers table (25 entries covering all timeouts, thresholds, and intervals). Reference files (1,292 lines across 6 files): agent-registry/README.md — full agent hierarchy diagram, all 17 pool supervisor detailed entries (purpose, worker count, sleep, worker tag pattern, special notes), worker-to-supervisor mapping table, utility subagent catalog (35+ entries), shared prompt fragment catalog. async-operations/README.md — why prompt_async exists (fire-and-forget vs blocking); complete OpenCode Server API reference (list sessions, create session, prompt_async, get status, get messages, get specific session, delete session) with curl examples and response shapes; full session naming convention with all supervisor and worker tag patterns in a table; common operations (starting supervisors/workers, checking status, detecting stuck sessions, cleanup); error handling policy (retry 3×). tracking-system/README.md — status vs announcement issue distinction; the one-at-a-time invariant; cycle number uniqueness; rolling average interval formula (0.90×old + 0.10×actual); CREATE_TRACKING_ISSUE step-by-step process; mandatory startup recovery protocol (READ then CREATE, with wrong-order warning); discovery patterns; announcement lifecycle; priority labels for announcements and when to use each; label rules (NEVER create; org-level only; always use forgejo-label-manager; forbidden Forgejo MCP tools list); forgejo-api skill curl patterns for label operations; complete automation-tracking-manager operations table. tier-system/README.md — four model tiers (haiku/codex/sonnet/opus) with model IDs, cost ranks, and use cases; how tier selectors work (pass-through inheritance mechanism, full call chain diagram); progressive escalation decision table; reading escalation history from attempt comments; human escalation trigger (Opus×3 same-problem) and steps; default model assignments for all agents grouped by model; runtime Gemini 2.5 Pro overrides. credential-flow/README.md — all environment variables with required/optional/ default columns; auto-detection of FORGEJO_URL/OWNER/REPO from git remote; credential hierarchy diagram; two bot accounts (primary vs reviewer) and why; worker credential rules (NEVER read env vars; everything from prompt); what a supervisor must include in every worker prompt; CA_MAX_PARALLEL_WORKERS formula with examples at N=1/4/8/16; security notes. coordination/README.md — claim protocol (CLAIM/HEARTBEAT/RELEASE comment prefixes); claim lifecycle; expiry (2 hours without heartbeat); availability check algorithm; exact comment formats for all three types; PR work conflict matrix (code-change vs merge-attempt vs review); session-level deduplication via tag search (primary mechanism); system-watchdog monitoring of violations; startup deduplication by product-builder; bot signature formats; announcement relevancy matrix quick reference table. ISSUES CLOSED: #0	2026-04-15 20:00:13 +00:00
freemo	47b4c5fbfb	docs(skill): final pass — 2 new trees, expanded trees, reference file completions ... SKILL.md (1,878 → 2,099 lines, 23 → 25 decision trees): New 'Is my work done?' tree — comprehensive Definition of Done checklist synthesising all requirements across implementation, three-level testing (unit/integration/benchmarks), coverage ≥ 97%, five CI quality checks, commit anatomy (atomic, body, footer), documentation (changelog, docstrings, CONTRIBUTORS.md), PR fields (description, dep direction, Epic scope, milestone, Type label), CI checks, and issue state transitions. New 'What design pattern should I use?' tree — all 24 patterns from CONTRIBUTING.md categorised across Creational (Factory, Abstract Factory, Builder, Prototype, Singleton, Object Pool, DI), Structural (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy, Module), Behavioral (Chain of Responsibility, Command, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, Visitor, Null Object), and Architectural (Repository, Unit of Work, Service Layer, MVC, CQRS, Event Sourcing, Specification). Every pattern includes a when-to-use description and a CleverAgents-specific example. Expand 'Am I about to write code?' — link to new patterns tree. Expand 'Am I writing tests?' — add And/But/Outline Gherkin keywords with examples, add Scenario Outline explanation, add naming good/bad examples with anti-pattern list, expand integration test guidance with what good integration tests exercise (CLI, DB, filesystem, service layer), expand Hypothesis section with 6 specific use cases and recommended strategies to build. Expand 'Am I about to commit?' — improve commit body guidance with a worked example showing what to write (context, why this approach, risks, caveats). Expand 'Am I triaging?' — add Epic/Legendary triage rules (no point estimates, no milestone assignment, sign-off labels required for closure). Add two branches to master decision tree for new trees. Reference files: references/testing/README.md (187 → 296 lines): - Add Gherkin Quality Guidelines section: Given/When/Then semantics table, Scenario Outline explanation with example, naming rules with good/bad table, common anti-patterns (implementation details, multiple behaviors, missing Then) - Add Property-Based Testing (Hypothesis) section: when-to-use table with 6 specific CleverAgents use cases, recommended strategies to build, integration with Behave step definitions with worked example references/langchain-langgraph/README.md (307 → 375 lines): - Add RxPY Reactive Streams section: Subject vs BehaviorSubject vs ReplaySubject decision table with when-to-use and code examples, key operators table with use cases and code examples, backpressure management patterns (debounce vs throttle_first with examples), and clear list of what RxPY is NOT for references/toolchain/README.md (271 → 272 lines): - Add Hypothesis to tool table (property-based testing, nox -s unit_tests) references/ci-cd/README.md (124 → 131 lines): - Fix project-specific version number in release example (v3.6.0 → generic v<MAJOR>.<MINOR>.<PATCH>) - Add release failure recovery procedure (verify secrets → build locally → delete tag → fix → re-tag) ISSUES CLOSED: #0	2026-04-15 19:40:35 +00:00
freemo	05e4f7446c	docs(skill): expand cleveragents-contributing SKILL.md — 5 new trees, all trees deepened ... Add 5 new decision trees: 'Should this be an Issue, Epic, or Legendary?' — hierarchy decision with one-commit test, demonstrable-capability test, strategic-pillar test, promotion/demotion rules, and quick self-test questions. 'Is this ticket well-scoped?' — all 11 quality criteria from CONTRIBUTING.md (Atomicity, Single Commit, Single Responsibility, Assignability, Verifiability, Self-Containment, Implementation Independence, Subtask Decomposition, Leaf Node, Mandatory Parent, Finite Completion) each with pass/fail test. 'What ticket state should this be in?' — full lifecycle state machine (Unverified → Verified → In progress → Paused → In review → Completed → Wont Do) with who can perform each transition and what labels are required. 'Am I triaging a ticket?' — maintainer triage 7-step process (duplicate check, validity assessment, completeness check, label assignment, milestone assignment, parent linking, bug companion TDD issue check). 'What branch name should I use?' — branch naming rules with all prefixes (feature/mN-, bugfix/mN-, tdd/mN-), source of milestone number N, kebab- case rules, traceability requirement (shared suffix between tdd/ and bugfix/ branches), and examples. Expand existing trees: 'Am I creating an issue?' — add 11 quality criteria summary, better acceptance criteria examples (good vs bad), note on Metadata section verbatim requirements. 'Am I about to write code?' — add SOLID principle explanations per letter, add WIP management section (git stash vs draft commits), add ADR step detail. 'Am I about to commit?' — add cosmetic-first-then-functional guidance, expand commit hygiene section with interactive rebase detail and goal of clean history (no wip commits). 'Am I submitting a PR?' — add post-submission CI failure handling (new commit not force-push), add major-change review handling (address every comment). 'Am I reviewing a PR?' — add blocking vs suggestion vs question comment distinction with examples, add approve-with-suggestions pattern, add no-wip- commits check in commit quality section. 'Am I writing tests?' — add integration vs e2e distinction (integration = real services; e2e = real LLM API keys), add Gherkin quality guidelines (Given/When/Then semantics, scenario naming, one behavior per scenario), add Hypothesis property-based testing section, expand test failure remediation to include real-bug-triggers-TDD-workflow path. 'Am I looking at a CI failure?' — add integration_tests failure diagnosis, add guidance for when unit test failure reveals a real bug (triggers full TDD workflow), expand benchmark-regression failure guidance. 'Am I documenting something?' — add CHANGELOG entry format (good vs bad examples), add ADR document structure (Title/Status/Context/Decision/ Consequences/Alternatives). 'Am I writing LangChain/LangGraph code?' — add RxPY reactive streams section (Subject, BehaviorSubject, ReplaySubject, operators, backpressure). 'Am I releasing a new version?' — add 'when to bump' section noting most PRs don't need bumps, add release failure recovery procedure (delete tag, fix, re-tag). Update master decision tree to add 5 new branches. Update Key Numbers table: add benchmark regression threshold (10%), cyclomatic complexity limit (>10), Hypothesis entry, benchmark regression threshold, issue quality criteria count, bug priority rule, TDD assignee preference. Update frontmatter to document new coverage. ISSUES CLOSED: #0	2026-04-15 19:32:10 +00:00
freemo	5a24b5bdf2	docs(skill): add cleveragents-spec skill from docs/specification.md ... New skill covering every architectural concept, entity, workflow, CLI command, and design decision from docs/specification.md (47,181 lines read in full). Explains WHAT the system is intended to build. SKILL.md (1,282 lines) — 18 decision trees: - 'What am I working on?' master routing tree - 'What is a Plan?' — 4 phases, reversion rules, hierarchy, decision tree - 'How does a plan run?' — step-by-step Action→Strategize→Execute→Apply - 'What is a Decision?' — 10 types, data model, dual tree+DAG structure, timing by phase, decision recording protocol - 'How do I correct a plan?' — revert vs append modes, Strategize vs Execute correction mechanics, affected subtree computation - 'What is an Invariant?' — 4 scopes, precedence chain (plan>action> project>global), non-overridable globals, Invariant Reconciliation Actor - 'What is an Actor?' — LLM vs graph types, Jinja2+env-var preprocessing, specialized roles (strategy/execution/estimation/invariant) - 'What is a Tool?' — 4 sources, capability metadata, 4-stage lifecycle, resource bindings and slots, anonymous tools, metadata overrides - 'What is a Validation?' — Tool subtype, always read-only, required vs informational modes, 3 attachment scopes, wrapping existing tools - 'What is a Skill?' — composition patterns, includes, tool overrides - 'What is a Resource?' — physical vs virtual, 34+ built-in types, DAG, type inheritance, 5-sandbox strategies, 6-level execution env routing, devcontainer auto-discovery and lazy activation - 'What is a Project?' — resource linking, multi-project plans, context config, execution environment - 'Which automation profile applies?' — 8 built-in profiles, 11 flags, Safety Profile, Automation Guard, Semantic Escalation, progressive trust - 'How does naming work?' — namespace format, types, ULID vs name identity - 'Which CLI command do I use?' — every command group with key flags - 'What is the architecture?' — 4 layers, 2 deployment modes, A2A protocol (full method routing, error codes, streaming), DI container - 'What is the ACMS?' — UKO, CRP, 10-slot pipeline, hot/warm/cold tiers - 'Which milestone am I in?' — v3.2.0–v3.8.0 status + cross-milestone invariants - Key Numbers table (35 entries) Reference files (1,974 lines across 9 files): - plan-lifecycle: phase mechanics, decision tree schema, checkpoint triggers, child plan execution modes, merge strategies, plan identity fields - entities: data models for Plan, Decision, Action, Session, Invariant, AutomationProfile, SafetyProfile, AutomationGuard, Namespace - architecture: 4-layer diagram, deployment modes, complete A2A method routing tables (standard + plan + registry + context + sync + health), streaming events, authentication, error taxonomy, full tech stack - automation-profiles: threshold table for all 8 built-in profiles, use cases, Semantic Escalation algorithm, custom profile YAML - actors-tools-skills: Actor/Tool/Validation/Skill YAML schemas with complete annotated examples, Jinja2 filter reference, LSP integration detail, LSPToolAdapter, actor context precedence - resources: complete resource type hierarchy (all 34+ types), sandbox strategies, type inheritance rules, execution environment routing, devcontainer integration, CLI usage - acms: UKO 4-layer ontology, CRP, 10-slot Context Assembly Pipeline with per-slot component names, hot/warm/cold eviction rules, skeleton compression, context view configuration - milestones: v3.2.0–v3.8.0 deliverables, architectural constraints, and definitions of done; cross-milestone quality gates and invariants - cli-commands: complete CLI reference for all command groups with all flags: plan, action, session, project, actor, skill, tool, validation, resource, invariant, automation-profile, lsp, config, utility ISSUES CLOSED: #0	2026-04-15 19:19:11 +00:00
freemo	38a2773261	docs(skill): expand cleveragents-contributing SKILL.md with 7 new trees and deep expansions ... Add 7 new decision trees covering gaps found in CONTRIBUTING.md audit: 'Am I creating an issue?' — full issue anatomy: mandatory Metadata section (exact commit message first line + branch name), Subtasks checkbox format with example, Definition of Done section, label rules (State/Unverified +Type+Priority; MoSCoW by owner only), Ref field rules, parent and blocking link mechanics via Forgejo dependencies, bug issues companion TDD issue rule. 'Am I about to write code?' — spec-first mandate (read docs/specification.md before any code), ADR process for architectural changes, branch must match issue Metadata, test-first requirement, SOLID + arg validation + type annotations requirements, prohibited list (# type: ignore, half-done work, mocks in src/, if-testing guards). 'Am I about to commit?' — self-review diff (git add -p), atomicity rules (one logical change, no cosmetic+functional mixing, code-move then modify), completeness rules (tests + docs + changelog + ancillary files in same commit), bisect-friendly / revertibility requirements, prescribed commit first line verbatim from issue Metadata, Commitizen usage, pre-commit hook rules, commit hygiene (topic branches, interactive rebase before merging). 'Am I submitting a PR?' — all 12 PR requirements numbered, with critical dependency direction rule (PR→blocks→issue; reversed = deadlock with full explanation), closing keywords, one Epic per PR, milestone + Type/ label, after-submission state transitions, complete merge checklist. 'Am I reviewing a PR?' — eligibility and approval rules, CI gate check, all 6 reviewer criteria (correctness, spec alignment, test quality, type safety, readability, performance, security, style, documentation, commit quality), requesting changes protocol, maintainer override rule. 'Am I documenting something?' — single canonical surface rule, traceability (module.class.method + commit hash; never file:linenum), same-commit rule, code-level docstring requirements, spec.md authority. 'Am I writing error handling?' — mandatory argument validation pattern (before ANY other logic) with Python code example, exception propagation rules (never suppress, never bare except, never return None on error), fail-fast principles, AssertionError for TDD expected-fail steps. Expand existing trees: - 'Am I writing tests?': add multi-level testing mandate (unit + integration + benchmarks required for every task), what tests must cover (error paths, edge cases, failure modes), test failure remediation rules - 'Which nox session?': clarify format vs format --check difference - 'Am I looking at a CI failure?': add quality/complexity failure diagnosis, common causes per job type, more detail on coverage and unit_tests failures - 'Am I writing LangChain/LangGraph code?': clarify MemorySaver requirement, memory class selection (Buffer vs Entity), format prohibition reasoning - 'Which directory?': add /benchmarks/ to directory tree Update master decision tree with 6 new branches for new trees. Update Key Numbers table with 4 new rows. Update frontmatter description to cover all new topics. Override highlights table: add commit first line and PR dep direction rows. ISSUES CLOSED: #0	2026-04-15 19:00:54 +00:00
freemo	82471f87f0	docs(skill): add cleveragents-contributing project-specific skill ... New skill covering all CONTRIBUTING.md project-specific rules that supplement or override the generic cleverthis-guidelines skill. Prominently declares override precedence at the top of SKILL.md and in every reference file — this skill's rules apply unconditionally when they conflict with the general skill. SKILL.md (839 lines) contains: - Override notice table comparing cleverthis-guidelines vs this project for 18 specific topics (framework, directories, tool names, etc.) - Master decision tree routing all project-specific situations - 9 detailed decision trees: file placement (exact directories), tests (Behave/Robot Framework rules), TDD bug fix workflow (full 6-step with branch naming), TDD issue-capture test (exact three-tag system with AssertionError enforcement), nox session reference (all sessions + CI job mappings + required-for-merge), CI failure diagnosis (per-job remediation), plan CLI (v3 vs legacy, ULID, storage backends), LangChain/LangGraph code (TypedDict, MemorySaver, BaseLanguageModel, FakeListLLM, canonical node pattern), Python imports (top-of-file, TYPE_CHECKING exception), dev env setup (complete tool inventory), and release process (backwards compat policy, Docker, secrets) - Key Numbers table with 33 project-specific values Reference files (1254 lines total): - testing/README.md: Behave rules, Robot Framework, TDD tag system with full examples and validation rules, AssertionError requirement, coverage threshold, mock placement, LangGraph testing, ASV benchmarks - ci-cd/README.md: all 13 CI jobs with nox session mappings, 3 workflow triggers, 5 required-for-merge checks, secrets table, caching policy, nightly quality sweep, branch protection - toolchain/README.md: complete nox session catalogue, Pyright prohibition on # type: ignore, ruff config, Hatch, pyproject.toml as single source, pre-commit setup, Commitizen, Python import rules with examples, error handling patterns with Python code - langchain-langgraph/README.md: TypedDict state, verb-based node naming, MemorySaver, conditional edges, BaseLanguageModel abstraction, prompt templates, sync+async requirement, output parsing, env var configuration, LangSmith disabled by default, retry decorators, canonical node template, FakeListLLM testing, state/workflow/streaming/memory test patterns - file-organization/README.md: exact directory map, per-directory rules and prohibitions, docs/specification.md authority, BDD step-file naming rules - cli-workflow/README.md: v3 vs legacy comparison table, ULID format, why mixing is impossible (separate storage backends), error diagnosis for common failure modes, manual migration steps, backwards compat policy ISSUES CLOSED: #0	2026-04-15 18:50:51 +00:00
freemo	caaafacf45	docs(skill): final pass — remove remaining project-specific language, add multi-language examples ... SKILL.md: - Remove stale 'v3 vs legacy plan workflow' reference from frontmatter description - Change all git tag version examples from project-specific v3.6.0 to generic v1.2.3 - Branch name example: upgrade-langchain -> upgrade-dependencies - Documentation traceability module path: was Python-only example, now shows Python, Java, TypeScript, and Go side by side - Task runner session tree: remove bare Python tool names from BEFORE SUBMITTING and SPECIFIC SITUATIONS subsections (bandit+semgrep+vulture, vulture, Radon, MkDocs, Robot Framework) — session descriptions are now tool-agnostic project-tools/README.md: - Full rewrite from Python-only reference to language-agnostic guide - Adds language/tooling note at top explaining Python/nox as the project example - Comprehensive equivalents table covering Python, JS/TS, Java/Kotlin, and Go for every concern (task runner, lint, format, type check, unit/integration tests, coverage, security scan, unused code, complexity, build, docs, benchmarks) - Project environment management section with language comparison table - Dependency caching section with per-language cache key patterns - Configuration files section as a multi-language comparison table - Development setup checklist shows nox/npm/gradlew/go alternatives side by side - 'Always Runnable' section with examples in all four ecosystems - git tag example: v3.6.0 -> v1.2.3 (generic) testing/README.md: - 'Never use stub/pass implementations' -> 'Never use empty/stub implementations (no no-op bodies)' — removes Python-keyword 'pass' used as if universal ISSUES CLOSED: #0	2026-04-15 18:39:22 +00:00
freemo	85ac059489	docs(skill): remove CleverAgents-specific content and finish tool generalisation ... Remove from SKILL.md and all reference files: - 'Am I choosing between Legacy and v3 plan workflow?' decision tree - LangChain/LangGraph sections (write-code tree, testing tree, code-style README, testing README) - FakeListLLM / MemorySaver / TypedDict LangGraph references - Backwards-compat pre-v3.0.0 policy block (project-version-specific) - v3 ULID format and Backwards-compat-starts rows from Key Numbers table - v3 Plan Lifecycle vs Legacy table from code-style README - Master-tree branch pointing to the v3/legacy workflow tree Generalise across all reference files: - commits/README: pre-commit checklist uses 'task runner session (e.g. nox -s X)' - pull-requests/README: fix approval count 2->1 with self-approval permitted; remove 'neither approver may be original author' (project allows self-approval); generalise automated-checks table command column - testing/README: remove LangChain/LangGraph Testing section; generalise all bare nox commands with task-runner framing and language note at top - code-style/README: rewrite General Principles to language-agnostic tooling guidance; generalise Import Guidelines with Python/Java/TS examples; rename and generalise Type Safety section; remove entire LangChain/LangGraph Best Practices section; remove entire v3 Plan Lifecycle vs Legacy section - security/README: generalise bare nox -s security_scan reference - issue-tracking/README: generalise subtask examples (Behave/nox) ISSUES CLOSED: #0	2026-04-15 18:32:33 +00:00
freemo	ca268e39fb	docs(skill): generalise SKILL.md for any programming language ... 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	2026-04-15 18:25:13 +00:00
freemo	d21edb67f7	docs(skill): expand cleverthis-guidelines SKILL.md with missing rules and new decision trees ... 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	2026-04-15 18:05:59 +00:00
freemo	8193545fb5	feat(skills): add cleverthis-guidelines agent skill ... Adds a comprehensive opencode skill under .opencode/skills/cleverthis-guidelines/ covering every rule, regulation, directive, and guideline governing CleverThis projects and company operations. Synthesized from CONTRIBUTING.md and the CleverThis Operations Code (C.O.C. v0.4, 70 pages). - 12 files, 2,384 lines across 11 reference categories - 1,059-line SKILL.md with 16 exhaustive decision trees covering every procedural situation: writing code, committing, submitting PRs, code review, creating issues, applying labels, ticket state transitions, sprint planning, triaging, point estimation, definition of done, authoring documents, confidentiality classification, security/credentials, FOSS, bug fixes (TDD), architectural decisions, and escalation paths Reference files cover: commits/ — Conventional Changelog format, atomic commit rules, pre-commit pull-requests/ — all 12 PR requirements, review process, merge criteria testing/ — BDD/Behave (unit), Robot Framework (integration), 97% coverage threshold (project-specific), TDD bug fix workflow, mocking rules issue-tracking/ — ticket hierarchy (Issue→Epic→Legendary), all quality criteria, mandatory issue sections, full label system (State/Type/Priority/ MoSCoW/Special), lifecycle flow, dependency direction rules sprints/ — DSDM, 6-stage triaging, MoSCoW, poker point estimation, all 4 sprint ceremonies with complete rule sets code-style/ — SOLID, design patterns, import rules, error handling, type safety, LangChain/LangGraph guidelines, v3 vs legacy plan lifecycle security/ — gopass-only password management, Yubikey rules, encryption policy information/ — 5 confidentiality stamp levels, document authoring, email conventions organizational/ — C-level hierarchy, ELB, OCRB, all 12 committees, personnel review project-tools/ — nox commands, CI/CD, release process, Hatch, Commitizen setup open-source/ — FOSS governance, open standards mandate, POSIX compliance Key project-specific facts documented: - Coverage threshold: 97% (overrides C.O.C. baseline of 85%) - BDD framework: Behave (not pytest alone) - Type checker: Pyright (never disabled, no type: ignore) - Bug fixes: mandatory TDD workflow with @tdd_expected_fail tagging	2026-04-15 17:51:07 +00:00
freemo	d9e5668cec	fix(skills): comprehensive final audit pass for programming-patterns skill ... 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	2026-04-15 13:22:13 -04:00
freemo	d33508e8c9	docs(skills): expand programming-patterns SKILL.md — 16 new trees, 5 new scenarios, 2 new sections ... Growth: 2,244 → 2,811 lines New decision trees added (51 → 67): GraphQL API, data validation & sanitization, payment processing, booking/reservation systems, recommendation engines, distributed locking, graceful startup/shutdown lifecycle, schema/data migration, SaaS onboarding wizards, social graphs, API SDK design, multi-step form/wizard UI, user preferences management, microservice chassis/platform, dependency injection containers, import/export systems New compound scenarios added (18 → 23): Scenario 19: Payment processing with provider failover Scenario 20: Hotel/resource booking with concurrent hold resolution Scenario 21: SaaS onboarding with multi-tenant provisioning Scenario 22: Distributed rate limiting across service instances Scenario 23: Recommendation engine with A/B testing and fallback New sections added: '🔗 Pattern Synergies' — 20-row table of patterns that are always better together '✅ Code Review Checklist' — 30-item pattern-coverage checklist for PRs covering every class, service, external call, conditional, loop, and test	2026-04-15 13:22:08 -04:00
freemo	81b318f07d	docs(skills): expand programming-patterns SKILL.md with 17 new decision trees and 6 new scenarios ... - 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)	2026-04-15 13:22:01 -04:00
freemo	98680825a7	feat(skills): add exhaustive programming patterns agent skill ... Adds a comprehensive opencode skill under .opencode/skills/programming-patterns/ covering 90+ design, architectural, concurrency, and functional patterns. - 108 files, 33,500+ lines across 13 reference categories - Every pattern: pseudocode + tested Python + Go + JavaScript implementations - All 239 code blocks verified passing (85 Python, 76 Go, 78 JS) - 1,569-line SKILL.md with: - Master decision tree (all 14 categories with multi-pattern suggestions) - 34 situation-specific decision trees covering every programming scenario (new feature, refactoring, REST API, CLI, data pipeline, rule engine, external integration, performance, memory, notifications, plugins, caching, events, auth, reporting, vendor lock-in, domain model, business rules, observability, file I/O, scheduling, testability, third-party libs, concurrency, complex domain interactions) - 12 compound pattern-combination scenarios with full architecture maps (e-commerce checkout, REST endpoint, background jobs, real-time dashboard, microservice resilience, ML pipeline, text editor, legacy migration, multi-tenant SaaS, document approval, financial transactions, chat) - 'When Am I Allowed to Skip Patterns?' mandate table (answer: never) - Quick pattern lookup tables for all 90+ patterns - Complete reference index	2026-04-15 13:21:51 -04:00
CleverAgents Build Agent	237e776951	feat(skills): add exhaustive Forgejo REST API agent skill ... Adds a comprehensive opencode skill under .opencode/skills/forgejo-api/ covering all 473 Forgejo REST API endpoints across 25 reference categories. - 78 files, 23,000+ lines, 149 distinct path parameter types - Every curl command parameterised ({owner}/{repo}/{index}/etc) and tested against the live git.cleverthis.com server - SKILL.md: 917-line entry point with quick-answer curl commands (35), jq cheat sheet for chaining API calls, 14 decision trees, 12 critical concepts (exclusive labels, lazy mergeability, SHA locking, auto-close keywords, search envelope differences, 412 stale-edit protection), full HTTP status code table, and environment variable reference - references/pull-requests/: CRUD, 6 merge styles, automerge, server-side rebase without local clone, inline review comments, diff/patch - references/issues/: comments, reactions, attachments, dependencies, time tracking, stopwatches, pinning - references/labels/: repo + org labels, exclusive label groups, GET/POST/PUT/DELETE on issues and PRs - references/ci-actions/ + references/commit-statuses/: workflow runs, dispatch, secrets, variables, quality gate verification - references/web-interface/ci-logs.md: step-by-step CI log access via CSRF web session (not available through REST API) - references/complex-workflows/: 10 multi-step recipes including PR review cycle, issue lifecycle, CI status check, server-side rebase, automerge, release workflow, org setup, fork contribution	2026-04-15 00:45:24 -04:00