feat(skills): pack assets, scripts, non-standard folders, and safe_mode into skill packages #169

Open

CoreRasurae wants to merge 2 commits from feature/m1-skill-directory-packing into develop

pull from: feature/m1-skill-directory-packing

merge into: cleveragents:develop

cleveragents:master

cleveragents:develop

cleveragents:tdd/m1-registry-resolve-full-type-names

cleveragents:bugfix/m1-inline-sandbox-import-restriction

cleveragents:feature/m2-reasoning-model-provider-support

cleveragents:feature/skill-package-support

cleveragents:feature/76-budget-pre-flight

cleveragents:feature/17-public-api

cleveragents:feature/m1-registry-http-client

cleveragents:master-backup

Conversation 2 Commits 2 Files changed 13 +1769 -13

CoreRasurae commented 2026-11-12 17:13:07 +00:00

Member

Copy link

Summary

• Add SkillDirectoryPacker / pack_skill_directory to turn an on-disk Agent Skills directory into one validated, content-addressed pkg_skl_ mapping.
• Add utils/pack_skill.py, a ready-to-use CLI: YAML to stdout by default, --output PATH for a publishable file, and --check for validate-only Package ID reporting.
• Preserve references/, assets/, scripts/, non-standard folders, and root files; store valid UTF-8 verbatim and other bytes as base64; emit safe_mode only for an explicit false.
• Add Behave coverage for round-trip, determinism, binary assets, safe_mode emission, invalid inputs, and CLI usage; add a Robot scenario that packs a real directory, publishes it as a local: package, and loads it end to end.
• Document both the Python API and the end-user CLI workflow with examples.
• Separate ci(benchmarks) commit: benchmark regression now resolves its baseline from the PR target branch (GITHUB_BASE_REF) or the active branch's stable base, instead of hard-coding origin/master.

Validation

• nox -s lint, nox -s format, nox -s typecheck
• nox -s unit_tests — 158 features / 3285 scenarios passed
• nox -s integration_tests — 381 tests passed
• nox -s coverage_report — 97.2% (>= 96.5% gate)
• nox -s security_scan, nox -s dead_code, nox -s complexity
• nox -s e2e_tests, nox -s docs, nox -s build
• nox -s benchmark
• nox -s benchmark_regression against origin/develop — no significant changes (the --quick informational CI mode is noisy; the full run is authoritative)
• New Behave CLI scenarios pass via nox -s unit_tests -- features/skill_directory_packages.feature

Closes #165

## Summary - Add `SkillDirectoryPacker` / `pack_skill_directory` to turn an on-disk Agent Skills directory into one validated, content-addressed `pkg_skl_` mapping. - Add `utils/pack_skill.py`, a ready-to-use CLI: YAML to stdout by default, `--output PATH` for a publishable file, and `--check` for validate-only Package ID reporting. - Preserve `references/`, `assets/`, `scripts/`, non-standard folders, and root files; store valid UTF-8 verbatim and other bytes as base64; emit `safe_mode` only for an explicit `false`. - Add Behave coverage for round-trip, determinism, binary assets, safe_mode emission, invalid inputs, and CLI usage; add a Robot scenario that packs a real directory, publishes it as a `local:` package, and loads it end to end. - Document both the Python API and the end-user CLI workflow with examples. - Separate `ci(benchmarks)` commit: benchmark regression now resolves its baseline from the PR target branch (`GITHUB_BASE_REF`) or the active branch's stable base, instead of hard-coding `origin/master`. ## Validation - `nox -s lint`, `nox -s format`, `nox -s typecheck` - `nox -s unit_tests` — 158 features / 3285 scenarios passed - `nox -s integration_tests` — 381 tests passed - `nox -s coverage_report` — 97.2% (>= 96.5% gate) - `nox -s security_scan`, `nox -s dead_code`, `nox -s complexity` - `nox -s e2e_tests`, `nox -s docs`, `nox -s build` - `nox -s benchmark` - `nox -s benchmark_regression` against `origin/develop` — no significant changes (the `--quick` informational CI mode is noisy; the full run is authoritative) - New Behave CLI scenarios pass via `nox -s unit_tests -- features/skill_directory_packages.feature` Closes #165

CoreRasurae added 2 commits 2026-11-12 17:13:08 +00:00

feat(skills): pack assets, scripts, non-standard folders, and safe_mode into skill packages ... fb4d5c56e5

Add a SkillDirectoryPacker facade and pack_skill_directory convenience function that turn an on-disk Agent Skills directory into a single validated pkg_skl_ package mapping. SKILL.md frontmatter is parsed into schema fields, the body becomes instructions, and every other file is preserved as a relative POSIX resource. Valid UTF-8 files stay verbatim while non-text files are base64-encoded. safe_mode is emitted only for an explicit false so the canonical safe default and existing Package IDs are preserved.

Refs: #165

ci(benchmarks): compare against the active branch baseline ... 7e49f8819c

Resolve the benchmark regression baseline from the pull request's target branch (GITHUB_BASE_REF) or, locally, from the stable branch the current checkout is based on, instead of always comparing against origin/master. Fetch the develop, master, and pull request target refs in CI so the resolved baseline is available.

Refs: #165

CoreRasurae added a new dependency 2026-11-12 17:14:05 +00:00

#165 feat(skills): pack assets, scripts, non-standard folders, and safe_mode into skill packages

CoreRasurae added 1 commit 2026-11-12 18:23:20 +00:00

feat(skills): add a CLI utility for packing skill directories ... eed7fb7a91

Add utils/pack_skill.py, a ready-to-use command-line front end for SkillDirectoryPacker. It writes the validated YAML mapping to stdout by default, supports --output for a publishable file, and --check for validation plus Package ID reporting. Diagnostics stay on stderr so stdout can be redirected or piped.

Cover the CLI with Behave scenarios and document both the Python API and the end-user CLI workflow. Include utils/ in the nox lint and format scopes.

Refs: #165

CoreRasurae force-pushed feature/m1-skill-directory-packing from eed7fb7a91 to acc51465da 2026-11-12 20:16:16 +00:00 Compare

hurui200320 approved these changes 2026-11-13 04:58:26 +00:00

hurui200320 left a comment

Copy link

PR Review: !169 (Ticket #165)

Verdict: Approve

The PR fully implements ticket #165 and ADR-2034 D-3/D-6 authoring tooling. All acceptance criteria are met and covered by tests: the packed mapping validates through the existing SkillValidator, determinism and binary/text round-trips are asserted, the safe_mode emission rule (emit only explicit false, normalize explicit true to absence) matches D-9 and §16.1–16.2, and the name/directory match check mirrors the external agentskills.io requirement. The frontmatter allowlist exactly covers the external spec's field set (name, description, license, compatibility, metadata, allowed-tools) plus the CleverActors safe_mode extension, so conformant external directories are not rejected. The symlink-escape guard (_ensure_within_root) and path validation correctly enforce §16.1 resource-path rules. Behave coverage is broad (28 scenarios, real filesystem/validator/canonicalizer, no mocks in the packing path), the Robot scenario exercises the real pack → local: publish → load pipeline end to end, and the guide documentation is accurate against the implementation. No critical or major issues found; the items below are robustness/test-gap improvements.

Critical Issues

None

Major Issues

None

Minor Issues

1. Unreadable resource files raise a raw OSError instead of SkillPackingError — src/cleveractors/agents/skill_packer.py:389-391. path.read_bytes() in _collect_resources can raise PermissionError/FileNotFoundError (also on TOCTOU deletion), which propagates unwrapped. The SKILL.md read path wraps this (skill_packer.py:305-308, and it is explicitly tested), so the resource path is inconsistent with the module's documented error contract; utils/pack_skill.py:74 only catches SkillPackingError, so the CLI prints a traceback and exits 1 instead of a clean error: ... with exit 2. Recommendation: wrap the resource read in the same except OSError → SkillPackingError("failed to read resource ...") handling and add a Behave scenario (e.g. chmod 000 resource) mirroring the unreadable-SKILL.md test.

2. No exclusion (or documentation) for VCS/OS junk — packing a checked-out skill repo embeds the whole .git database — src/cleveractors/agents/skill_packer.py:378-396. Path.rglob("*") matches dot-files and recurses into dot-directories, so a directory that is a git checkout (the normal distribution form for agentskills.io skills) packs .git/HEAD, .git/objects/** (binary, base64), plus .DS_Store/__pycache__ etc. into resources. This bloats the single content-addressed blob and changes the Package ID with unrelated VCS state. Not a spec violation (the format permits any additional directory) and the ID stays deterministic, but it is a silent footgun for the tool's primary use case. Recommendation: at minimum document the "everything is packed, including hidden files" behavior in docs/guides/skill-packages.md; preferably skip well-known junk (e.g. .git, __pycache__, .DS_Store) or offer an ignore mechanism.

3. Test gap: a directory containing only SKILL.md is never packed — features/skill_directory_packages.feature. No scenario covers the no-resources case, so the if resources: branch at src/cleveractors/agents/skill_packer.py:271-272 (omit the resources key entirely) is untested even though D-2/§16.1 make resources optional. Recommendation: add a scenario asserting a SKILL.md-only directory packs successfully and that the mapping has no resources key.

4. New utils/pack_skill.py sits outside every static-analysis gate except ruff — pyproject.toml:109-114 (pyright include = ["src"]), bandit/vulture target src/cleveractors only, and coverage sources exclude it. The file is fully annotated, but nothing enforces it. Recommendation: add "utils" to the pyright include list (or document why the CLI is deliberately excluded from the strict gates).

Nits

1. CLI: --check silently ignores --output — utils/pack_skill.py:78. Erroring or warning on the mutually confusing combination would be friendlier; args.output.write_text() (utils/pack_skill.py:94) can also raise an uncaught OSError (e.g. missing parent dir) producing a raw traceback instead of a clean message.
2. UTF-8 BOM in SKILL.md is rejected as "must start with YAML frontmatter" — src/cleveractors/agents/skill_packer.py:107. \ufeff is not stripped by .strip(), and Windows-authored SKILL.md files commonly carry a BOM. Consider tolerating/stripping a leading BOM or documenting the restriction.
3. Real-world ecosystem skills with client-specific frontmatter will be rejected with "unsupported field(s)" (src/cleveractors/agents/skill_packer.py:320-325). This is a deliberate, tested, documented design choice and the safe default (vs. silently dropping fields), but the guide could tell authors the workaround: move client-specific keys into metadata.
4. SkillPackingError(ValueError) breaks the project's exception-hierarchy convention — src/cleveractors/agents/skill_packer.py:68. Every other domain error derives from CleverAgentsException; consider multiple inheritance (CleverAgentsException, ValueError) so generic handlers still catch it.
5. ${{ github.base_ref }} is interpolated directly into the CI run: script — .gitea/workflows/ci.yml:376-377. Standard Actions hardening is env: indirection. Low risk here since base_ref is limited to existing branch names in the base repo.
6. Mixed-concern PR — the ci(benchmarks) commit (1dda265) rides in the feat(skills) PR. It is disclosed in the PR description, is small and sensible (the dynamic baseline resolution is correct, including the GITHUB_BASE_REF → origin/<base> mapping and the develop-before-master ancestor fallback), so this is non-blocking — just slightly off the atomic-commit convention.

Summary

A high-quality, well-tested implementation of the directory-to-package packing tooling that ticket #165 and ADR-2034 D-3/D-6 call for. The core packing logic is correct and deterministic: frontmatter parsing (including both allowed-tools spellings and the canonical safe_mode rule), UTF-8/base64 classification, POSIX path normalization, symlink-escape protection, and Package ID computation via the existing validator/canonicalizer all check out against §16 and the ADR, and every ticket acceptance criterion has a matching scenario (28 Behave scenarios plus a real end-to-end Robot publish-and-load test). The minor items above are robustness polish — chiefly consistent OSError wrapping for resource reads, an explicit stance (and test) on the SKILL.md-only and hidden/.git-file cases — and none block merge.

## PR Review: !169 (Ticket #165) ### Verdict: Approve The PR fully implements ticket #165 and ADR-2034 D-3/D-6 authoring tooling. All acceptance criteria are met and covered by tests: the packed mapping validates through the existing `SkillValidator`, determinism and binary/text round-trips are asserted, the `safe_mode` emission rule (emit only explicit `false`, normalize explicit `true` to absence) matches D-9 and §16.1–16.2, and the name/directory match check mirrors the external agentskills.io requirement. The frontmatter allowlist exactly covers the external spec's field set (name, description, license, compatibility, metadata, allowed-tools) plus the CleverActors `safe_mode` extension, so conformant external directories are not rejected. The symlink-escape guard (`_ensure_within_root`) and path validation correctly enforce §16.1 resource-path rules. Behave coverage is broad (28 scenarios, real filesystem/validator/canonicalizer, no mocks in the packing path), the Robot scenario exercises the real pack → `local:` publish → load pipeline end to end, and the guide documentation is accurate against the implementation. No critical or major issues found; the items below are robustness/test-gap improvements. ### Critical Issues None ### Major Issues None ### Minor Issues 1. **Unreadable resource files raise a raw `OSError` instead of `SkillPackingError`** — `src/cleveractors/agents/skill_packer.py:389-391`. `path.read_bytes()` in `_collect_resources` can raise `PermissionError`/`FileNotFoundError` (also on TOCTOU deletion), which propagates unwrapped. The SKILL.md read path wraps this (`skill_packer.py:305-308`, and it is explicitly tested), so the resource path is inconsistent with the module's documented error contract; `utils/pack_skill.py:74` only catches `SkillPackingError`, so the CLI prints a traceback and exits 1 instead of a clean `error: ...` with exit 2. Recommendation: wrap the resource read in the same `except OSError → SkillPackingError("failed to read resource ...")` handling and add a Behave scenario (e.g. chmod 000 resource) mirroring the unreadable-SKILL.md test. 2. **No exclusion (or documentation) for VCS/OS junk — packing a checked-out skill repo embeds the whole `.git` database** — `src/cleveractors/agents/skill_packer.py:378-396`. `Path.rglob("*")` matches dot-files and recurses into dot-directories, so a directory that is a git checkout (the normal distribution form for agentskills.io skills) packs `.git/HEAD`, `.git/objects/**` (binary, base64), plus `.DS_Store`/`__pycache__` etc. into `resources`. This bloats the single content-addressed blob and changes the Package ID with unrelated VCS state. Not a spec violation (the format permits any additional directory) and the ID stays deterministic, but it is a silent footgun for the tool's primary use case. Recommendation: at minimum document the "everything is packed, including hidden files" behavior in `docs/guides/skill-packages.md`; preferably skip well-known junk (e.g. `.git`, `__pycache__`, `.DS_Store`) or offer an ignore mechanism. 3. **Test gap: a directory containing only `SKILL.md` is never packed** — `features/skill_directory_packages.feature`. No scenario covers the no-resources case, so the `if resources:` branch at `src/cleveractors/agents/skill_packer.py:271-272` (omit the `resources` key entirely) is untested even though D-2/§16.1 make `resources` optional. Recommendation: add a scenario asserting a SKILL.md-only directory packs successfully and that the mapping has no `resources` key. 4. **New `utils/pack_skill.py` sits outside every static-analysis gate except ruff** — `pyproject.toml:109-114` (pyright `include = ["src"]`), bandit/vulture target `src/cleveractors` only, and coverage sources exclude it. The file is fully annotated, but nothing enforces it. Recommendation: add `"utils"` to the pyright `include` list (or document why the CLI is deliberately excluded from the strict gates). ### Nits 1. **CLI: `--check` silently ignores `--output`** — `utils/pack_skill.py:78`. Erroring or warning on the mutually confusing combination would be friendlier; `args.output.write_text()` (`utils/pack_skill.py:94`) can also raise an uncaught `OSError` (e.g. missing parent dir) producing a raw traceback instead of a clean message. 2. **UTF-8 BOM in `SKILL.md` is rejected as "must start with YAML frontmatter"** — `src/cleveractors/agents/skill_packer.py:107`. `\ufeff` is not stripped by `.strip()`, and Windows-authored SKILL.md files commonly carry a BOM. Consider tolerating/stripping a leading BOM or documenting the restriction. 3. **Real-world ecosystem skills with client-specific frontmatter will be rejected** with "unsupported field(s)" (`src/cleveractors/agents/skill_packer.py:320-325`). This is a deliberate, tested, documented design choice and the safe default (vs. silently dropping fields), but the guide could tell authors the workaround: move client-specific keys into `metadata`. 4. **`SkillPackingError(ValueError)` breaks the project's exception-hierarchy convention** — `src/cleveractors/agents/skill_packer.py:68`. Every other domain error derives from `CleverAgentsException`; consider multiple inheritance (`CleverAgentsException, ValueError`) so generic handlers still catch it. 5. **`${{ github.base_ref }}` is interpolated directly into the CI `run:` script** — `.gitea/workflows/ci.yml:376-377`. Standard Actions hardening is `env:` indirection. Low risk here since `base_ref` is limited to existing branch names in the base repo. 6. **Mixed-concern PR** — the `ci(benchmarks)` commit (1dda265) rides in the `feat(skills)` PR. It is disclosed in the PR description, is small and sensible (the dynamic baseline resolution is correct, including the `GITHUB_BASE_REF` → `origin/<base>` mapping and the develop-before-master ancestor fallback), so this is non-blocking — just slightly off the atomic-commit convention. ### Summary A high-quality, well-tested implementation of the directory-to-package packing tooling that ticket #165 and ADR-2034 D-3/D-6 call for. The core packing logic is correct and deterministic: frontmatter parsing (including both `allowed-tools` spellings and the canonical `safe_mode` rule), UTF-8/base64 classification, POSIX path normalization, symlink-escape protection, and Package ID computation via the existing validator/canonicalizer all check out against §16 and the ADR, and every ticket acceptance criterion has a matching scenario (28 Behave scenarios plus a real end-to-end Robot publish-and-load test). The minor items above are robustness polish — chiefly consistent `OSError` wrapping for resource reads, an explicit stance (and test) on the SKILL.md-only and hidden/`.git`-file cases — and none block merge.

hurui200320 approved these changes 2026-11-13 04:58:33 +00:00

CoreRasurae force-pushed feature/m1-skill-directory-packing from acc51465da to 2c9d06e9fd 2026-11-13 12:17:20 +00:00 Compare

Some checks failed

Hide all checks

CI / lint (pull_request) Successful in 42s

Details

CI / typecheck (pull_request) Successful in 1m29s

Details

CI / quality (pull_request) Successful in 1m29s

Details

CI / security (pull_request) Successful in 1m33s

Details

CI / build (pull_request) Successful in 2m26s

Details

CI / integration_tests (pull_request) Successful in 3m25s

Details

CI / unit_tests (pull_request) Successful in 6m13s

Details

CI / coverage (pull_request) Successful in 5m20s

Details

CI / status-check (pull_request) Successful in 7s

Details

CI / benchmark (pull_request) Failing after 28m1s

Details

This pull request can be merged automatically.

You are not authorized to merge this pull request.

View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.

git fetch -u origin feature/m1-skill-directory-packing:feature/m1-skill-directory-packing

git switch feature/m1-skill-directory-packing

Sign in to join this conversation.

Reviewers

No reviewers

hurui200320

Labels

Clear labels

  

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/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

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks

#165 feat(skills): pack assets, scripts, non-standard folders, and safe_mode into skill packages

cleveragents/cleveractors-core

Reference

cleveragents/cleveractors-core!169

No description provided.