Skip to content
This repository was archived by the owner on Jul 29, 2026. It is now read-only.

Addressing PR comments - #100

Merged
erinepshovel-code merged 4 commits into
mainfrom
copilot/fix-code-for-review-comments
Jun 7, 2026
Merged

erinepshovel-code merged 4 commits into
mainfrom
copilot/fix-code-for-review-comments

Conversation

Copilot AI commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

No description provided.

Copilot AI changed the title [WIP] Fix code based on review comments fix(docs): align manifest vendoring SHA in README with PR description Jun 4, 2026
Copilot AI requested a review from erinepshovel-code June 4, 2026 11:57
@erinepshovel-code
erinepshovel-code marked this pull request as ready for review June 6, 2026 04:43
Copilot AI review requested due to automatic review settings June 6, 2026 04:43

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the agent-skill documentation to correctly record the upstream skill-lib commit SHA used when vendoring the manifest/ skill, preventing future maintainers from chasing an incorrect upstream reference.

Changes:

  • Updated the documented vendored-from SHA for manifest/ from 546b45b to d6e4d78 in .agents/skills/README.md.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 38b9ee6460

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .agents/skills/README.md
- `meta-module-build/` — metadata-first module scaffolding
- `manifest/` — living-spec generator for `CLAUDE.md` (vendored from
`The-Interdependency/skill-lib@546b45b`). Generates the mechanical facts
`The-Interdependency/skill-lib@d6e4d78`). Generates the mechanical facts

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the final vendoring SHA

This points the manifest skill provenance at an earlier re-vendor commit, but the merge commit that introduced the skill has a later ci(manifest) step that says the checksum is identical to skill-lib@546b45b and that it bumped the source ref. Since manifest/SKILL.md tells reviewers to verify generate.py.sha256 against the recorded SHA, recording d6e4d78 sends future updates/audits to the wrong upstream version and reintroduces the provenance mismatch this README entry was meant to prevent.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@codex[agent] repair

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary

  • Restored the manifest/ skill provenance entry to the final vendoring SHA, The-Interdependency/skill-lib@546b45b, addressing the review feedback that d6e4d78 pointed at the earlier re-vendor source rather than the later recorded source ref.
  • Committed the fix as 4ab2e48 (fix(docs): restore manifest vendoring SHA) and created a follow-up PR.

Testing

  • cd .agents/skills/manifest && sha256sum -c generate.py.sha256
  • python .agents/skills/manifest/generate.py --pyproject backend/pyproject.toml --check
  • git diff --check

View task →

@Codex Codex AI changed the title fix(docs): align manifest vendoring SHA in README with PR description Addressing PR comments Jun 7, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 158af8d86b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .agents/skills/README.md
- `meta-module-build/` — metadata-first module scaffolding
- `manifest/` — living-spec generator for `CLAUDE.md` (vendored from
`The-Interdependency/skill-lib@546b45b`). Generates the mechanical facts
`The-Interdependency/skill-lib@d6e4d78`). Generates the mechanical facts

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the final manifest source SHA

The merge commit that introduced this skill first mentions d6e4d78, but its final ci(manifest) step says the pinned checksum is identical to skill-lib@546b45b and the README introduced by that merge recorded 546b45b. Since manifest/SKILL.md tells maintainers to verify the vendored generate.py.sha256 against the recorded source SHA, changing this line to the earlier re-vendor commit sends future audits to the wrong upstream artifact.

Useful? React with 👍 / 👎.

@erinepshovel-code
erinepshovel-code merged commit 0e2b459 into main Jun 7, 2026
7 checks passed
@erinepshovel-code
erinepshovel-code deleted the copilot/fix-code-for-review-comments branch June 7, 2026 02:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants