Repository profile

first-tree

Review Skills in first-tree-ai/first-tree, with license, maintenance context, and source paths.

Skills
4
Repository stars
139
Identity status
Source-linked

Provenance

Source and identity

Source-linked
Profile type
Repository
Canonical name
first-tree
Public sources
1
License context
Apache-2.0

Source entries

Agent Skills from first-tree

Repository stars and maintenance signals provide context, but do not automatically become an individual Skill's quality score.

Computed 92139

first-tree-ai/first-tree

context-tree-review

Review a GitHub pull request or GitLab merge request against the workspace-bound Context Tree when a trusted server-authored Context Reviewer run supplies provider-scoped authority. Repair every safely determined finding with the host git and forge CLI identity, then use GitHub App review plus exact-head merge or GitLab note plus exact-SHA merge. Do not use for code changes, ordinary tree reads or writes, or default-branch audits.

Computed 92139

first-tree-ai/first-tree

first-tree-read

Read the applicable Context Tree before acting. In BYO sessions, route only among locally authorized Teams by reading each exact root SCOPE.md before selecting one task snapshot; in managed workspaces, use the bound Tree. Do not use for a Context Tree PR/MR review or an explicit broad audit of stored tree content.

Computed 93139

first-tree-ai/first-tree

first-tree-seed

Bootstrap a team's Context Tree from readable source repos — for an onboarding "build / set up the Context Tree" task on a tree that has no domain structure yet: either no tree exists (creates and binds it) or a bound-but-empty tree (fills it). Supports clean explicit-Team invocation without a Workspace manifest, managed briefing, or prior setup-chat transcript, while preserving managed-workspace compatibility. Proposes an initial top-level + second-level domain structure for approval, then draf

Computed 94139

first-tree-ai/first-tree

first-tree-write

Source-driven Context Tree write workflow for managed and BYO consumers. BYO always requires the exact SCOPE-routed read snapshot and a new user confirmation of the precise Team/source/targets/mutation plan before any Tree mutation. If no source artifact is available, there is no write task.

Pinned paths

Every entry links to a specific source path and commit when available.

Repository context

Activity, license, and repository-level popularity are shown as context.

Open the source

Inspect the public repository