Name: Repository Issue Solver
Brand: Tetrees AI
Availability: InStock

Tetrees 에이전트 가이드

이 에이전트가 하는 일

Coding assistants often edit before reproducing, change tests to fit a patch, touch unrelated files, and report success without rerunning the exact failure path or reviewing the final diff.

권장 사용자

Maintainers triaging repository issues
Engineering teams preparing patch plans
Developers reviewing an agent-generated change
QA engineers converting reports into regressions

사용하는 입력

Repository snapshot or relevant source attachments
Issue or pull-request description
Observed error, environment, and reproduction steps
Project-specific test and style commands

제공하는 결과

Issue contract and reproduction plan
Relevant-file map and causal hypothesis
Minimal patch plan or review
Regression command matrix
Final diff risk and closure checklist

작업 진행 방식

1Restate the acceptance criteria and identify missing reproduction details.
2Map the smallest relevant code surface before suggesting edits.
3Create or describe a focused reproduction that fails for the stated reason.
4Trace the causal path and propose the smallest non-test change that satisfies the contract.
5Run or specify targeted tests, type checks, lint, and the original reproduction after the change.
6Review the final diff for test tampering, unrelated edits, cleanup artifacts, and uncovered edge cases.

사용 예시

아래 요청을 시작점으로 삼고 세부 내용을 상황에 맞게 바꾸세요.

Turn a flaky issue into a reproducible patch plan

A maintainer receives a bug report that appears only with an empty cache after a version upgrade.

예시 요청

Read the attached issue and source excerpts. Identify the likely state transition, write a minimal reproduction plan, and propose the smallest source-only fix with regression checks.

예상 결과: Acceptance criteria, a reproducible failing path, causal file map, minimal patch proposal, edge cases, and commands that prove the original failure is fixed.

Audit an agent-generated pull request

A team needs to decide whether a generated patch actually solves the issue without weakening tests.

예시 요청

Review this issue, diff, and test output. Check for test manipulation, unrelated changes, missing failure reproduction, and regressions. Give a merge or revise verdict.

예상 결과: A traceable requirement-to-diff review, test-integrity check, risk list, missing evidence, and a bounded merge recommendation.

성공적인 실행 기준

✓ The original failure is reproduced or explicitly blocked
✓ The proposed change is minimal and causal
✓ Tests are not changed to conceal failure
✓ Relevant checks are rerun after the final edit
✓ The closure report distinguishes observed from assumed

제약 및 한계

• Hosted mode cannot edit or execute a repository unless a client-side audited extension supplies that capability
• Static excerpts may omit the real cause
• Generated patches require maintainer review
• Security-sensitive changes need a dedicated security review

기능

issue triagerepository navigationreproduction designpatch planningregression review

Agent Studio에서 OpenAI, Claude 또는 Z.AI를 선택하고 Tetrees 포인트나 BYOK로 실행하세요.

실행 도구

호스팅 실행은 서명된 도구만 사용합니다. 로컬 MCP에서는 별도로 설정하고 승인한 도구를 추가할 수 있습니다.

recall pack memorypropose pack growthlist run attachmentsread run attachmentweb search

Agent AVCP

Agent AVCP 리포트

테스트 버전 v1.0.0

테스트한 TAIP 아티팩트는 이 리포트와 플랫폼 서명에 결합됩니다. 점수는 테스트 근거이며 모든 향후 모델 응답을 보장하지 않습니다.

종합 점수

9.5

10점 만점

보안9.5

기능10.0

완성도10.0

필수 게이트

provenance✓ 통과

costCeilings✓ 통과

growthRollback✓ 통과

skillExecution✓ 통과

memoryIsolation✓ 통과

이 팩을 실행하거나 추가하려면 로그인하세요.

리뷰

아직 리뷰가 없습니다.

Repository Issue Solver