cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

feature/m3-agent-skills-loader #416

Closed
aditya wants to merge 4 commits from feature/m3-agent-skills-loader into master
pull from: feature/m3-agent-skills-loader
merge into: cleveragents:master
Conversation 2 Commits 4 Files changed 28 +6463 -13
aditya commented 2026-02-24 13:49:55 +00:00
Member
Copy link

Description

Implements the Agent Skills Standard loader (M2.4a) for CleverAgents v3.
Adds AgentSkillLoader — a three-tier progressive disclosure engine that
parses SKILL.md files into structured tool definitions and registers them
in the Tool Registry with namespaced naming and read-only defaults.

Key additions:

  • SkillStep — structured step objects parsed from the frontmatter steps: list with stable 1-based indexing
  • AgentSkillSpec — full SKILL.md parser (frontmatter + Markdown body)
  • AgentSkillToolDescriptor — lightweight tool registry view with source="agent_skill", read_only=True, and read-only resource_slots
  • AgentSkillResourceSlot — binding slots for discovered scripts/, references/, assets/ directories
  • AgentSkillLoader — progressive disclosure lifecycle: discover() → activate() → list_resources() → deactivate()
  • docs/reference/agent_skills.md — full reference covering folder layout, SKILL.md format, structured steps, resource binding slots, and tool mapping

Type of Change

  • New feature (non-breaking change which adds functionality)
  • Documentation update
  • Test improvements

Quality Checklist

  • Code follows the project's coding standards (see CONTRIBUTING.md)
  • All public/protected methods have argument validation
  • Static typing is complete (no Any unless justified)
  • nox -s typecheck passes with no errors
  • nox -s lint passes with no errors
  • Unit tests written/updated (Behave scenarios in features/)
  • Integration tests written/updated (Robot suites in robot/) if applicable
  • Coverage remains above 85% (nox -s coverage_report)
  • No security issues introduced (nox -s security_scan)
  • No dead code introduced (nox -s dead_code)
  • Documentation updated if behavior changed

Testing

Unit tests follow the BDD-first approach defined in CONTRIBUTING.md.
50 Behave scenarios cover all public API paths with 100% branch and
statement coverage on agent_skills_loader.py. 9 Robot Framework
integration tests verify end-to-end behaviour against the sample skill
folder at examples/agent-skills/deploy-to-staging/.

Test Commands Run

nox -s lint             # Ruff lint + format — passed
nox -s typecheck        # Pyright static analysis — passed
nox -s security_scan    # Bandit — no issues
nox -s dead_code        # Vulture — no dead code
nox -s unit_tests       # 50 Behave scenarios — all passed
nox -s integration_tests # 9 Robot Framework tests — all passed
nox -s coverage_report  # 100% branch+statement on agent_skills_loader.py

Related Issues

Closes #160

Implementation Notes

Progressive disclosure follows the three-tier model from docs/specification.md § AgentSkillAdapter:

  • Tier 1 (discover()) — name + description only, ~50–100 tokens
  • Tier 2 (activate()) — full SKILL.md Markdown body loaded into active context
  • Tier 3 (list_resources()) — file paths from scripts/, references/, assets/ on demand

Structured steps are declared in the SKILL.md frontmatter as a YAML list under the steps: key. Each entry becomes a SkillStep(index, content) with a guaranteed stable 1-based index, enabling the agent to reference specific steps by number without relying on body text parsing.

Resource binding slots are emitted as AgentSkillResourceSlot entries in the tool descriptor — one per discovered sub-directory. All slots are unconditionally access="read_only" since Agent Skills may never write to their own resource directories.

Namespaced naming follows the namespace/short_name convention (ADR-002). Both segments must be alphanumeric with hyphens/underscores; violation raises a ValueError with an actionable message.

No existing behaviour was changed. All additions are net-new classes and functions inside src/cleveragents/skills/.

## Description Implements the Agent Skills Standard loader (`M2.4a`) for CleverAgents v3. Adds `AgentSkillLoader` — a three-tier progressive disclosure engine that parses `SKILL.md` files into structured tool definitions and registers them in the Tool Registry with namespaced naming and read-only defaults. Key additions: - `SkillStep` — structured step objects parsed from the frontmatter `steps:` list with stable 1-based indexing - `AgentSkillSpec` — full SKILL.md parser (frontmatter + Markdown body) - `AgentSkillToolDescriptor` — lightweight tool registry view with `source="agent_skill"`, `read_only=True`, and read-only `resource_slots` - `AgentSkillResourceSlot` — binding slots for discovered `scripts/`, `references/`, `assets/` directories - `AgentSkillLoader` — progressive disclosure lifecycle: `discover()` → `activate()` → `list_resources()` → `deactivate()` - `docs/reference/agent_skills.md` — full reference covering folder layout, SKILL.md format, structured steps, resource binding slots, and tool mapping ## Type of Change - [x] New feature (non-breaking change which adds functionality) - [x] Documentation update - [x] Test improvements ## Quality Checklist - [x] Code follows the project's coding standards (see CONTRIBUTING.md) - [x] All public/protected methods have argument validation - [x] Static typing is complete (no `Any` unless justified) - [x] `nox -s typecheck` passes with no errors - [x] `nox -s lint` passes with no errors - [x] Unit tests written/updated (Behave scenarios in `features/`) - [x] Integration tests written/updated (Robot suites in `robot/`) if applicable - [x] Coverage remains above 85% (`nox -s coverage_report`) - [x] No security issues introduced (`nox -s security_scan`) - [x] No dead code introduced (`nox -s dead_code`) - [x] Documentation updated if behavior changed ## Testing Unit tests follow the BDD-first approach defined in `CONTRIBUTING.md`. 50 Behave scenarios cover all public API paths with 100% branch and statement coverage on `agent_skills_loader.py`. 9 Robot Framework integration tests verify end-to-end behaviour against the sample skill folder at `examples/agent-skills/deploy-to-staging/`. ### Test Commands Run ```bash nox -s lint # Ruff lint + format — passed nox -s typecheck # Pyright static analysis — passed nox -s security_scan # Bandit — no issues nox -s dead_code # Vulture — no dead code nox -s unit_tests # 50 Behave scenarios — all passed nox -s integration_tests # 9 Robot Framework tests — all passed nox -s coverage_report # 100% branch+statement on agent_skills_loader.py ``` ## Related Issues Closes #160 ## Implementation Notes **Progressive disclosure** follows the three-tier model from `docs/specification.md § AgentSkillAdapter`: - Tier 1 (`discover()`) — name + description only, ~50–100 tokens - Tier 2 (`activate()`) — full SKILL.md Markdown body loaded into active context - Tier 3 (`list_resources()`) — file paths from `scripts/`, `references/`, `assets/` on demand **Structured steps** are declared in the SKILL.md frontmatter as a YAML list under the `steps:` key. Each entry becomes a `SkillStep(index, content)` with a guaranteed stable 1-based index, enabling the agent to reference specific steps by number without relying on body text parsing. **Resource binding slots** are emitted as `AgentSkillResourceSlot` entries in the tool descriptor — one per discovered sub-directory. All slots are unconditionally `access="read_only"` since Agent Skills may never write to their own resource directories. **Namespaced naming** follows the `namespace/short_name` convention (ADR-002). Both segments must be alphanumeric with hyphens/underscores; violation raises a `ValueError` with an actionable message. **No existing behaviour was changed.** All additions are net-new classes and functions inside `src/cleveragents/skills/`.
feat(skill): add MCP adapter for external tools
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 15s
Details
CI / build (pull_request) Successful in 16s
Details
CI / quality (pull_request) Successful in 21s
Details
CI / security (pull_request) Successful in 33s
Details
CI / typecheck (pull_request) Successful in 47s
Details
CI / integration_tests (pull_request) Successful in 2m54s
Details
CI / unit_tests (pull_request) Successful in 6m13s
Details
CI / docker (pull_request) Successful in 39s
Details
CI / benchmark-regression (pull_request) Successful in 19m58s
Details
CI / coverage (pull_request) Failing after 22m0s
Details
a6e56fe96e
Merge branch 'master' into develop-aditya-2
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / build (pull_request) Successful in 17s
Details
CI / quality (pull_request) Successful in 20s
Details
CI / typecheck (pull_request) Successful in 47s
Details
CI / security (pull_request) Successful in 50s
Details
CI / integration_tests (pull_request) Successful in 3m41s
Details
CI / unit_tests (pull_request) Successful in 7m9s
Details
CI / docker (pull_request) Successful in 38s
Details
CI / benchmark-regression (pull_request) Successful in 20m12s
Details
CI / coverage (pull_request) Successful in 24m15s
Details
80a56846fe
 
# Conflicts:
#	implementation_plan.md
feat(skill): add agent skills loader
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 16s
Details
CI / build (pull_request) Successful in 17s
Details
CI / lint (pull_request) Successful in 21s
Details
CI / typecheck (pull_request) Successful in 30s
Details
CI / security (pull_request) Successful in 50s
Details
CI / integration_tests (pull_request) Successful in 4m0s
Details
CI / unit_tests (pull_request) Successful in 13m51s
Details
CI / docker (pull_request) Successful in 1m23s
Details
CI / benchmark-regression (pull_request) Successful in 21m50s
Details
CI / coverage (pull_request) Successful in 48m58s
Details
6267504006
 
Implement AgentSkillSpec loader that parses SKILL.md frontmatter and
progressive disclosure sections into structured SkillStep objects with
stable 1-based index ordering. Map Agent Skills to tool descriptors with
namespaced naming (namespace/short_name), read-only defaults
(read_only=True, writes=False), and read-only AgentSkillResourceSlot
entries for each discovered resource directory (scripts/, references/,
assets/). Add explicit validation for missing/invalid frontmatter fields
(name, description) and the optional steps list. Add
docs/reference/agent_skills.md describing folder layout, parsing rules,
step structure, resource binding slots, and tool mapping.

Tests: 50 Behave scenarios (100% branch+statement coverage on loader),
9 Robot Framework integration tests, ASV benchmarks for parsing
throughput and lifecycle performance.

ISSUES CLOSED: #160
brent.edwards approved these changes 2026-02-24 19:14:34 +00:00
brent.edwards left a comment
Copy link

This passes all tests, though you will need to merge the file src/cleveragents/skills/__init__.py.

It has my approval.

This passes all tests, though you will need to merge the file `src/cleveragents/skills/__init__.py`. It has my approval.
freemo requested changes 2026-02-24 22:26:55 +00:00
Dismissed
freemo left a comment
Copy link

Code Review: PR #416 — feature/m3-agent-skills-loader

The PR description is thorough and well-written, with clear quality checklist and implementation notes. The agent skills loader implementation itself looks solid. However, there are several structural and process issues that need to be addressed.

Critical Issues

1. No milestone assigned (CONTRIBUTING.md §11)
This PR is not assigned to any milestone. The linked issue #160 is on milestone v3.1.0 — this PR must be assigned to the same milestone. "A PR without a milestone will not be reviewed."

2. Multiple unrelated features bundled (CONTRIBUTING.md §2)
This PR contains 3 distinct features from 3 separate issues:

  • feat(skill): add agent skills loader — issue #160, branch should be feature/m3-agent-skills-loader
  • feat(skill): add MCP adapter for external tools — issue #159, branch should be feature/m3-mcp-adapter
  • feat(actor): extend hierarchical actor YAML schema and loader — no clear issue match

Per guidelines: "Each PR must be associated with a single Epic. Do not combine work from multiple unrelated Epics in one PR." These should be separate PRs, each scoped to a single feature/issue.

3. Not mergeable
The PR has merge conflicts with master that must be resolved before review can complete.

4. Missing commit issue references (CONTRIBUTING.md §4)
Only 1 of 3 feature commits (feat(skill): add agent skills loader) has an issue reference (ISSUES CLOSED: #160). The other two commits (feat(skill): add MCP adapter for external tools and feat(actor): extend hierarchical actor YAML schema and loader) have no issue reference in their footers.

5. No CHANGELOG update (CONTRIBUTING.md §6)
Three new features were added with no CHANGELOG entries.

6. No CONTRIBUTORS.md update (CONTRIBUTING.md §8)
Aditya Chhabra should be added to CONTRIBUTORS.md if not already listed.

Code Quality Issues

7. registry: Any in MCPToolAdapter.register_tools() (Type Safety)
The registry parameter is typed as Any instead of the concrete ToolRegistry type. Per CONTRIBUTING.md Type Safety guidelines: "never use inline comments or annotations to suppress individual type checking errors." If this is to avoid circular imports, use a TYPE_CHECKING forward reference:

from __future__ import annotations
from typing import TYPE_CHECKING
if TYPE_CHECKING:
    from cleveragents.skills import ToolRegistry

8. Bare except Exception: in adapter.py:disconnect()
The disconnect method catches Exception without binding the variable. While exc_info=True logs the traceback, this is overly broad. Per guidelines: "Do not use bare catch-all exception handlers without re-raising unless you have specific recovery logic."

9. Broad exception handling in connect() and invoke()
adapter.py uses except Exception as exc catch-alls in both methods. Consider catching more specific exceptions.

What's Good

  • Excellent PR description with quality checklist
  • Proper Closes #160 issue linking
  • Comprehensive testing (50 Behave scenarios, 9 Robot tests, ASV benchmarks)
  • Good progressive disclosure architecture
  • Proper file placement in correct directories
  • Strong argument validation in public methods

Recommended Path Forward

  1. Split into 3 separate PRs (agent skills loader, MCP adapter, actor hierarchy) each with their own issue reference.
  2. Assign milestone v3.1.0.
  3. Add CHANGELOG and CONTRIBUTORS.md entries.
  4. Fix type annotation on registry parameter.
  5. Resolve merge conflicts.
## Code Review: PR #416 — `feature/m3-agent-skills-loader` The PR description is thorough and well-written, with clear quality checklist and implementation notes. The agent skills loader implementation itself looks solid. However, there are several structural and process issues that need to be addressed. ### Critical Issues **1. No milestone assigned (CONTRIBUTING.md §11)** This PR is not assigned to any milestone. The linked issue #160 is on milestone v3.1.0 — this PR must be assigned to the same milestone. "A PR without a milestone will not be reviewed." **2. Multiple unrelated features bundled (CONTRIBUTING.md §2)** This PR contains **3 distinct features** from 3 separate issues: - `feat(skill): add agent skills loader` — issue #160, branch should be `feature/m3-agent-skills-loader` - `feat(skill): add MCP adapter for external tools` — issue #159, branch should be `feature/m3-mcp-adapter` - `feat(actor): extend hierarchical actor YAML schema and loader` — no clear issue match Per guidelines: "Each PR must be associated with a single Epic. Do not combine work from multiple unrelated Epics in one PR." These should be separate PRs, each scoped to a single feature/issue. **3. Not mergeable** The PR has merge conflicts with `master` that must be resolved before review can complete. **4. Missing commit issue references (CONTRIBUTING.md §4)** Only 1 of 3 feature commits (`feat(skill): add agent skills loader`) has an issue reference (`ISSUES CLOSED: #160`). The other two commits (`feat(skill): add MCP adapter for external tools` and `feat(actor): extend hierarchical actor YAML schema and loader`) have no issue reference in their footers. **5. No CHANGELOG update (CONTRIBUTING.md §6)** Three new features were added with no CHANGELOG entries. **6. No CONTRIBUTORS.md update (CONTRIBUTING.md §8)** Aditya Chhabra should be added to CONTRIBUTORS.md if not already listed. ### Code Quality Issues **7. `registry: Any` in `MCPToolAdapter.register_tools()` (Type Safety)** The `registry` parameter is typed as `Any` instead of the concrete `ToolRegistry` type. Per CONTRIBUTING.md Type Safety guidelines: "never use inline comments or annotations to suppress individual type checking errors." If this is to avoid circular imports, use a `TYPE_CHECKING` forward reference: ```python from __future__ import annotations from typing import TYPE_CHECKING if TYPE_CHECKING: from cleveragents.skills import ToolRegistry ``` **8. Bare `except Exception:` in `adapter.py:disconnect()`** The disconnect method catches `Exception` without binding the variable. While `exc_info=True` logs the traceback, this is overly broad. Per guidelines: "Do not use bare catch-all exception handlers without re-raising unless you have specific recovery logic." **9. Broad exception handling in `connect()` and `invoke()`** `adapter.py` uses `except Exception as exc` catch-alls in both methods. Consider catching more specific exceptions. ### What's Good - Excellent PR description with quality checklist - Proper `Closes #160` issue linking - Comprehensive testing (50 Behave scenarios, 9 Robot tests, ASV benchmarks) - Good progressive disclosure architecture - Proper file placement in correct directories - Strong argument validation in public methods ### Recommended Path Forward 1. Split into 3 separate PRs (agent skills loader, MCP adapter, actor hierarchy) each with their own issue reference. 2. Assign milestone v3.1.0. 3. Add CHANGELOG and CONTRIBUTORS.md entries. 4. Fix type annotation on `registry` parameter. 5. Resolve merge conflicts.
freemo dismissed freemo's review 2026-02-24 22:45:34 +00:00
Reason:

dont want hard block

aditya closed this pull request 2026-02-25 14:24:32 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / quality (pull_request) Successful in 16s
Required
Details
CI / build (pull_request) Successful in 17s
Required
Details
CI / lint (pull_request) Successful in 21s
Required
Details
CI / typecheck (pull_request) Successful in 30s
Required
Details
CI / security (pull_request) Successful in 50s
Required
Details
CI / integration_tests (pull_request) Successful in 4m0s
Required
Details
CI / unit_tests (pull_request) Successful in 13m51s
Required
Details
CI / docker (pull_request) Successful in 1m23s
Required
Details
CI / benchmark-regression (pull_request) Successful in 21m50s
Details
CI / coverage (pull_request) Successful in 48m58s
Required
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No reviewers
CoreRasurae
brent.edwards
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!416
No description provided.