Skip to content

Bring the Spec's Python Profile Text Onto the Per-Directory Rule #3552

Closed

Description

@ptr727

Summary

After #3492, CODESTYLE.md "Python" and python-codestyle's references/profiles.md say a profile belongs to a declared directory, not to the repository. Two spec texts still state the per-repository model:

  • spec/type-model.md "Profiles: build vs lint-only" has a language type declare its profile once, at one depth for the repository.
  • spec/project-types.json python.profileNote describes lint-only as "stdlib-only utility scripts embedded in a non-Python repo" and build as "the repo's deliverable". profiles.md no longer uses either phrase.

The audit spec cites CODESTYLE.md as the intent for python.profile.detect, so the spec now disagrees with the doc it cites.

Expected

The spec text describes the Python profile per declared directory and drops the two phrases, matching profiles.md. Whether type-model.md keeps a per-repository depth for other languages is a separate question for the same change.

🤖 Generated with Claude Code

Activity

  1. ptr727 commented on Oct 28, 2026

    @ptr727
    OwnerAuthor

    Backlog burndown round 3 claim, one group for #3548, #3550, #3552 and #3554. Branch: feature/3548-python-profile-followups. Predicted file set: .agents/skills/python-codestyle/SKILL.md, .agents/skills/python-codestyle/references/profiles.md (the "Adapt before propagating" text), spec/type-model.md and spec/project-types.json (their Python profile text only), plus regenerated copies under .github/skills/ and .claude-plugin/fleet-skills/ (skill files and .source-digests/ entries) for python-codestyle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions