Skip to content

feat: add shared SCORE coding instructions#55

Open
FScholPer wants to merge 1 commit into
mainfrom
split/pr51-instructions
Open

feat: add shared SCORE coding instructions#55
FScholPer wants to merge 1 commit into
mainfrom
split/pr51-instructions

Conversation

@FScholPer
Copy link
Copy Markdown

@FScholPer FScholPer commented May 15, 2026

Scope

This PR adds the shared SCORE instruction pack under .github/instructions/.

Why

Extracted from oversized PR #51 to keep review focused and faster.

Out of scope

  • governance schemas and manifest
  • copier template distribution
  • docs and hygiene automation

Validation

  • one focused branch/commit slice for shared instructions

Merge Order

  1. feat: add SCORE governance core contracts #54 (core contracts)
  2. feat: add shared SCORE coding instructions #55 (instruction pack)
  3. feat: add copier template for governance distribution #56 (copier template)
  4. chore: add markdown hygiene checks and governance docs #57 (docs and hygiene)

Relationship to original PR

This PR is part of the split of oversized PR #51.


ALWAYS create new objects, NEVER mutate existing ones:
- Return new instances rather than modifying in place
- Use spread operators, `List.copyOf()`, `Map.copyOf()`, or equivalent
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

This seems to be for Java??

## Pre-Commit Checklist
- [ ] All tests pass locally
- [ ] No lint errors or warnings
- [ ] No `console.log` / `System.out.println` left in production code
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

JavaScript and Java specific??

Copy link
Copy Markdown

@a-zw a-zw left a comment

Choose a reason for hiding this comment

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

Seems to be just AI-slop instead of sensible coding instructions aligned to S-CORE needs.

- Avoid deep nesting; break logic into helpers

## Dependencies & Configuration
- Pin all dependency versions in `requirements.txt` or `pyproject.toml`
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

We use Bazel here, so we do it differently.

## Mandatory Checks Before Every Commit
- [ ] No hardcoded secrets (API keys, passwords, tokens)
- [ ] All user inputs validated at system boundaries
- [ ] SQL injection prevention (parameterized queries only)
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Are actually using any SQL anywhere in S-CORE?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants