EcoPasteHub
Official@ecopastehub · China
Offers architectural specification management and compliance verification for software development lifecycles through structured repository analysis and state tracking.
Agent Skills by EcoPasteHub
Showing 24 vetted skills indexed across 1 GitHub repositories.
EcoPasteHubtrellis-spec-bootstrap
Generate project-specific Trellis coding specs from real codebase analysis.
EcoPasteHubtrellis-before-dev
Loads project coding guidelines from .trellis/spec before starting development tasks.
EcoPasteHubtrellis-brainstorm
Guides requirements discovery interviews and produces PRD, design, and implementation planning artifacts.
EcoPasteHubtrellis-break-loop
Analyzes fixed bugs to identify root causes and capture prevention mechanisms into specs.
EcoPasteHubtrellis-session-insight
Search and extract past AI conversation history via the trellis mem CLI.
EcoPasteHubtrellis-check
Verifies code changes against specs, lint, type checks, tests, and cross-layer consistency.
EcoPasteHubtrellis-meta
Guides AI agents in understanding and customizing local Trellis architecture within user projects.
EcoPasteHubtrellis-channel
Coordinate multi-agent collaboration through Trellis channel event logs, workers, and forum threads.
EcoPasteHubtrellis-update-spec
Captures executable contracts and coding conventions into .trellis/spec/ documentation files.
EcoPasteHubsync-zh-changelog
Synchronize EcoPaste release sections from CHANGELOG.md into the Chinese changelog with structural validation.
EcoPasteHubtrellis-finish-work
Archives completed tasks and records session journals after verifying git working tree state.
EcoPasteHubtrellis-continue
Resumes in-progress tasks by loading the Trellis workflow phase index and step context.
EcoPasteHubtrellis-spec-bootstrap
Create and update coding specifications by analyzing repository architecture with GitNexus and ABCoder.
EcoPasteHubtrellis-before-dev
Review pre-development checklists and spec indexes for coding guideline compliance.
EcoPasteHubtrellis-brainstorm
Guide collaborative product requirements discovery through structured interviews and codebase exploration.
EcoPasteHubtrellis-break-loop
Analyze bug fixes to identify root causes and update specs.
EcoPasteHubtrellis-session-insight
Retrieve past AI conversation history from Claude Code, Codex, and Pi Agent sessions.
EcoPasteHubtrellis-check
Run spec compliance, linting, type-checking, and testing on code changes.
EcoPasteHubtrellis-meta
Modify Trellis architecture files and platform directories in user projects.
EcoPasteHubtrellis-channel
Manage multi-agent collaboration through shared event logs and worker spawning.
EcoPasteHubtrellis-update-spec
Capture and document executable contracts and coding conventions from completed tasks.
EcoPasteHubtrellis-start
Initialize a development session by extracting workflow guides and classifying tasks.
EcoPasteHubtrellis-finish-work
Archive completed tasks and record session progress in the .trellis environment.
EcoPasteHubtrellis-continue
Resume interrupted workflow tasks by interpreting state from .trellis/workflow.md.
Frequently Asked Questions About EcoPasteHub
FAQPage SchemaWhat specific development tasks does EcoPasteHub enable?▼
EcoPasteHub enables the creation and maintenance of coding specifications, automated compliance linting, and the systematic archiving of project progress. It facilitates structured product requirements discovery and ensures that bug fixes are documented as updated architectural specifications within the project environment.
Which personas benefit most from these technical capabilities?▼
Software architects, lead developers, and technical project managers benefit from these capabilities. The system is designed for teams requiring strict adherence to coding conventions, consistent documentation of executable contracts, and reliable state tracking across complex, multi-contributor development sessions.
What are the prerequisites for implementing these specifications?▼
Implementation requires a project environment capable of hosting .trellis directories and associated configuration files. Users must have existing repository architecture accessible for analysis and be prepared to integrate the provided specification-tracking logic into their existing development lifecycle and session management routines.