Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Add a loop-audit skill

未关闭
#26 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start by reading parent issue #15 and inspect the repository’s existing skills, README, go-help rows, validation, and build entry points; the payload does not name their paths. Map the eight feedback loops and stage placement, then add the loop-audit skill with its three references and the requested handoff. Done means the skill audits a real project, identifies and fixes the weakest loop, passes the stated validation and build, and includes current vendor facts.

由索引模型根据 Issue 内容生成。

描述

ready-for-agent

Parent

#15

What to build

A repo owner runs a new loop-audit skill and sees which feedback loops the project has and which it lacks. The loops are agent rules, static checks, git hooks, end-to-end proof, failure output, CI, nightly checks, and post-deploy smoke checks. Each loop is listed with its real command or "missing, proposed: …". The audit names the weakest loop and builds the first fix, so it ends in a change, not a report.

The skill places each check by its speed:

  • Staged-file checks under ten seconds run on pre-commit.
  • Checks under two minutes run on pre-push.
  • CI is the clean-environment superset.
  • Nightly runs only the slow checks that catch drift. Each nightly failure becomes an issue, a PR, or a file an agent can read.

The audit flags quiet bypasses of the guardrails: an edited hook config, CI workflow, or lint config, a narrowed glob, a removed or renamed check, and a step moved to a later stage. When the user's project-guardrails skill is installed, the audit sends static-check setup to it instead of repeating it.

Acceptance criteria

  • The loop-audit skill exists, with references for the stage placement table, the nightly example, and the anti-bypass checklist.
  • Run once on a real project, the audit lists every loop with a command or a proposal, names the weakest loop, and builds a fix for it.
  • With project-guardrails installed, the audit hands static-check setup to it.
  • Vendor facts in the references, such as hook manager flags and action versions, match current docs.
  • The skill has a go-help row and a README line, and passes the authoring-a-skill validation and the build.
主要语言
TypeScript
星标
0
派生
0
平均合并
3 小时 33 分钟
30 天内合并 PR
13

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

gregogun/gstack 的其他 Issue

查看 gregogun/gstack 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。