integration-hardening
Use for GitHub/GitLab/Linear wiring in rust-harness to remove stub-token paths, enforce env-driven credential resolution, and add regression tests for real-client behavior with safe fallbacks.
来源信息
- 仓库
- ryanmaclean/tundra
- 最近来源活动
- 2026年2月22日 04:08
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 0
- 分支
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- integration-hardening
- description
- Use for GitHub/GitLab/Linear wiring in rust-harness to remove stub-token paths, enforce env-driven credential resolution, and add regression tests for real-client behavior with safe fallbacks.
- allowed_tools
- ["Bash","Read","Edit","Write"]
- references
- ["/Users/studio/rust-harness/crates/at-core/src/config.rs","/Users/studio/rust-harness/crates/at-bridge/src/http_api.rs","/Users/studio/rust-harness/crates/at-integrations/src/gitlab/mod.rs","/Users/studio/rust-harness/crates/at-integrations/src/linear/mod.rs"]
# Integration Hardening
## Trigger
Use this skill when changing GitHub/GitLab/Linear endpoints, token handling, or import/review flows.
## Rules
1. Never hardcode `"stub-token"` or `"stub-key"` in API handlers.
2. Resolve token env names from `Config.integrations.*_token_env`.
3. Return actionable `503` with `env_var` when missing credentials.
4. Preserve runtime stub fallback only inside integration clients for explicit test tokens.
5. Keep route comments truthful (remove "(stubs)" when real wiring is present).
## Regression Checklist
1. Missing token path returns `503` + env var name.
2. Configured token path constructs real client.
3. Existing tests still pass in no-network environments.
4. API response shape remains backward-compatible unless explicitly versioned.
## Preferred Test Scope
- Unit tests for client fallback behavior.
- Handler tests for auth/config edge cases.
- Targeted `cargo check -p at-bridge -p at-integrations`.
在 GitHub 查看