tecton

Execute Tecton plans and tests with Pants in data-science repos.

21|2|Updated Dec 20, 2021
One-click install
npx skills add https://github.com/ferdinandyb/dotfiles --skill tecton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tecton
Source: https://github.com/ferdinandyb/dotfiles/tree/main/.config/opencode/skill/skills/tecton
Command: npx skills add https://github.com/ferdinandyb/dotfiles --skill tecton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and execute Tecton plans and tests within the data-science repo, ensuring long-running commands are captured and displayed safely.

Core Features & Use Cases

  • Plan tecton plans against a workspace and review the generated plan.
  • Run tecton tests with Pants and inspect results using controlled logging and output capture.
  • Workspace-aware execution for staging and development environments with the option to skip tests.

Quick Start

Run pants tecton-plan with --workspace=<workspace> --skip-tests to generate a plan and view results.

Frequently Asked Questions about tecton

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run tecton-plan and tecton-test-run within a data-science repository?

You can run tecton-plan and tecton-test-run within a data-science repository by using Pants to execute the commands with controlled logging and workspace-aware staging environments.

Can I skip tests when generating a tecton plan for a specific workspace?

Yes, you can skip tests when generating a tecton plan by running the Pants command with the --skip-tests flag and specifying your target workspace.

What is the best way to capture output from long-running Tecton commands?

The best way to capture output from long-running Tecton commands is to use a workspace-aware execution approach that provides robust output capture and streaming for safe result inspection.

Does Tecton testing with Pants enforce specific environment requirements?

Yes, Tecton testing with Pants enforces environment requirements to ensure plans and tests execute correctly within the data-science repository staging and development workspaces.

Why does my tecton plan execution lose output during long-running tasks?

Tecton plan execution loses output during long-running tasks when lacking robust output capture and streaming, which this workspace-aware Pants workflow provides for controlled logging and inspection.

How do I inspect tecton test results using controlled logging?

You inspect tecton test results by running tests with Pants, which captures output and uses controlled logging to display the results of long-running commands safely.