zhengyh avatar

zhengyh

Community

@dev2019zheng

9Followers
|
130Public Repos
|
10Published Skills

私欲日生,如地上尘,一日不扫,便又有一层。着实用功,便见道无终穷,愈探愈深,必使精白无一毫不彻方可。

Skills Distribution
DomainDeveloper To...Spec-Driven Develo.. (35%)Code Quality Verif.. (25%)Requirements Engin.. (20%)Session & Task Lif.. (20%)

Agent Skills by zhengyh

Showing 10 vetted skills indexed across 1 GitHub repositories.

Frequently Asked Questions About zhengyh

FAQPage Schema
What tasks can I accomplish with zhengyh's Trellis skills?

You can bootstrap .trellis/spec coding guidelines, inject project conventions before coding, run collaborative requirements discovery with PRD seeding, verify code quality against specs, analyze bug root causes, and manage session start, resume, and wrap-up for development tasks.

Who should use the Trellis skill suite?

Software engineers and developers practicing spec-driven development who want persistent, project-specific coding guidelines. It suits individuals or teams maintaining .trellis/spec documentation, running pre-commit quality gates, and preserving debugging knowledge across sessions.

How does a typical Trellis development session run?

Start with trellis-start to load guidelines, git status, and active tasks, which routes to brainstorm, direct edit, or task flow. Use trellis-continue to resume in-progress phases, trellis-check before committing, and trellis-finish-work to archive tasks and record progress.

What are the prerequisites for using these Trellis skills?

You need a project initialized with trellis init, producing a .trellis directory with spec documents, platform hooks, settings, and task structures. Codebase analysis optionally uses GitNexus, ABCoder, or direct source inspection; trellis-continue relies on get_context.py --mode phase.

How does Trellis prevent recurring bugs and knowledge loss?

trellis-break-loop analyzes root cause categories, why prior fixes failed, and prevention mechanisms after each bug fix. trellis-update-spec then captures executable contracts and conventions learned from debugging or discussion into .trellis/spec documents for future sessions.